innerHTML getter for <style> in XML document is inconsistent with the setter
Reported by
bzbar...@mit.edu,
Apr 22 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:48.0) Gecko/20100101 Firefox/48.0 Example URL: See attached testcase. Steps to reproduce the problem: 1. Load attached testcase. 2. Observe two alerts showing different text What is the expected behavior? The two alerts should show the same text. What went wrong? Things keep being escaped when serialized on get but not parsed as markup when the set happens. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 51.0.2704.19 (Official Build) dev (64-bit) Channel: n/a OS Version: OS X 10.10 Flash Version: Shockwave Flash 21.0 r0 Per spec, I would think that the set should actually parse the given string as markup, but I'm not sure whether that's web-compatible at first glance.... Filed https://github.com/w3c/DOM-Parsing/issues/6 on that. But in any case, the serializer should be consistent with the parser. <script> has the same issue.
,
Apr 23 2016
Yes, that is odd.
,
May 30 2016
,
May 30 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 30 2017
,
Jul 2
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 10
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dtapu...@chromium.org
, Apr 22 2016