source element not being interpreted inside noscript
Reported by
jonathan...@gmail.com,
Aug 8 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3180.0 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Add a picture element with source files inside a noscript tag 2. Disable Javascript 3. View the picture What is the expected behavior? When JavaScript is disabled, I would expect the source elements inside the noscript tag to be run as normal What went wrong? The image given in the img tag was rendered rather than the image in the source tag Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 62.0.3180.0 Channel: dev OS Version: 4.12.4-1-ARCH Flash Version:
,
Aug 9 2017
Here is an example on codepen. A picture of a dog is in the source element in a noscript element. I would expect to see a dog if JS is switched off and a Cat if switched on. https://codepen.io/Jab2870/full/NvjrrK/
,
Aug 10 2017
Tested this issue on Ubuntu 14.04 using reported dev version # 62.0.3180.0. Following are the steps followed to reproduce the issue: 1.Navigated to sample link provided in comment #2 i.e; https://codepen.io/Jab2870/full/NvjrrK/ 2.Disabled Javascript and Observed that picture doesnot change even on switching Off javascript Attaching screenshot for reference. reporter@ Could you please check attached screencast and confirm us if we have missed any steps in reproducing the issue. Note: If this issue is consistently reproducible, this may be related to Linux-ARCH specific. Thanks!
,
Aug 10 2017
Yes, that is correct. Since creating this bug, I have also tested on other systems including 60.0.3112.90 on windows 10. It does not appear to be specific to linux. I have also tested in FireFox and the same bug appears to be present there.
,
Aug 10 2017
Thank you for providing more feedback. Adding requester "jbanavatu@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 11 2017
Per C#4 Issue is seen on Firefox as well and I was able to reproduce the same on on older(45.0.2454.101) as well as the latest(62.0.3181.0) chrome version on Windows-10, Mac OS 10.12.5 and Linux Ubuntu 14.04. Not sure what's the correct behavior here. I am marking this Untriaged for more inputs and further investigation by the respective team.
,
Aug 14 2017
I have also created a big in Firefox's bug tracker. Interesting discussion might also take place there: https://bugzilla.mozilla.org/show_bug.cgi?id=1390100
,
Aug 18 2017
According to the current specification, <source> must be a child of <picture>. In this case, the <source> is a child of <noscript>. The current behavior is correct. If you think this behavior is wrong, please raise an issue to a standard body.
,
Aug 18 2017
I agree that the picture spec says that the source elements should be directed children, but the noscript spec says that when JS is disabled / not available, the contents of the noscript tag should represent it's contents and the tag itself should be transparent. I interpreted that to mean that when JS is disabled, the noscript element should represent the source elements and therefore would be a direct child of the picture element. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 Deleted