UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Example URL:
https://codepen.io/AmeliaBR/pen/RgMZJN/

Steps to reproduce the problem:
1. Create an inline SVG within a non-XML HTML file.

2. Use HTML markup inside a <title> or <desc> in that SVG (this is valid, and is still parsed fine).

3. Add a <script> or <style> section later in the SVG, using <![CDATA[...]]> around the content (which is valid within SVG in HTML, and is parsed fine in other cases).

What is the expected behavior?
The HTML parser should accept the CDATA notation within inline SVG, dropping it from the text passed to the CSS parser / JS interpreter.

See https://html.spec.whatwg.org/multipage/syntax.html#cdata-sections

What went wrong?
The CDATA bits are treated as plain text, and cause the CSS/JS to break.  But only if there had been previous HTML-in-SVG-metadata in the document.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: 

PS. HTML elements in an SVG <foreignObject> don't seem to cause the same problem.