New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 648294 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Contents of String Inside Script Tag Are Rendered to the Screen

Reported by jviny...@uship.com, Sep 19 2016

Issue description

Chrome Version       : 54.0.2840.27 beta-m (64-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox: OK
         IE: OK

What steps will reproduce the problem?
(1) Load the attached html file in the Chrome beta version mentioned above


What is the expected result?
None of the contents of the script tag should be rendered to the screen.


What happens instead?
Parts of a javascript string inside the script tag are rendered to the screen.


Please provide any additional information below. Attach a screenshot if
possible.


 
test.html
683 bytes View Download
ChromeSreenshot.PNG
30.6 KB View Download
Components: Blink>HTML>Parser
Status: Untriaged (was: Unconfirmed)
Fascinating; good minimal repro. Removing the SVG or LINK elements breaks the repro.

Comment 2 by jviny...@uship.com, Oct 5 2016

Interestingly, it looks like this issue is fixed in Chrome Canary v55.0.2880.4 canary (64-bit).  Wondering if the fix will make its way into beta as well?
Owner: dominicc@chromium.org
Status: WontFix (was: Untriaged)
Thank you for filing this bug.

This might be related to  Issue 639541 , you could try to reproduce it before/after r421177 to be sure, or try it in the latest Chrome 54 beta where we reverted something.

By the way, I expect that file will be parsed by the HTML parser, so you might find more idiomatic markup, like not using /> closing tag syntax but closing tags which aren't self-closing, etc.

It sounds like this has been fixed in the interim so I'm marking this as WontFix/Obsolete. Please let me know if you see this in recent betas (eg 54.0.2840.50.)

Sign in to add a comment