Bug 191061 – Parsing noscript tag with an img child element inside a figure tag fires wrongly a fetch

• Status: RESOLVED
• Resolution: INVALID
• Component: DOM

[Dimitrios Grammatikogiannis]

Created attachment 353359 [details]
bug preview

For the following snippet the image should be ignored if javascript is enabled but an extra fetch event is fired

```html
<figure>
  <noscript>
    <img src="https://webkit.org/wp-content/uploads/safari.png" alt=""/>
  </noscript>
</figure>
```

You can check it live also here: https://codepen.io/dgrammatiko/pen/xyNXjv

There shouldn't be an extra fetch in this case, respect the noscript tag

[Simon Fraser (smfr)]

Is this the preload scanner?

[Rob Buis]

(In reply to Dimitrios Grammatikogiannis from comment #0)
> Created attachment 353359 [details]
> bug preview
> 
> For the following snippet the image should be ignored if javascript is
> enabled but an extra fetch event is fired
> 
> ```html
> <figure>
>   <noscript>
>     <img src="https://webkit.org/wp-content/uploads/safari.png" alt=""/>
>   </noscript>
> </figure>
> ```
> 
> You can check it live also here: https://codepen.io/dgrammatiko/pen/xyNXjv
> 
> There shouldn't be an extra fetch in this case, respect the noscript tag

Hi Dimitrios, I can't repro this, the preload scanner does not preload this image, and the image element in the no script tag is not created as DOM node. Can you give some more detailed steps how you are seeing the extra fetch?

[Dimitrios Grammatikogiannis]

> Can you give some more detailed steps how you are seeing the extra fetch?

I'm afraid this was a false report, the problem was not in Safari (I've been tricked by codepen auto reload) but in the intersection observer polyfill.