181642 2018-01-14 23:38:43 -0800 insertAdjacentHTML of string including elements with prefixed attributes not working 2023-10-23 17:14:27 -0700 1 1 1 Unclassified WebKit XML Safari Technology Preview Unspecified Unspecified NEW P2 Normal --- 66424 1 mail webkit-unassigned ahmad.saleem792 annevk ap cdumez mail rniwa wenson_hsieh oldest_to_newest 1389241 0 mail 2018-01-14 23:38:43 -0800 1. Load an XML file, for example one of the files inside an ODT or DOCX file. 2. Try to insert a string in a place where this is valid at the end using element.insertAdjacentHTML('beforeend', string) or element.innerHTML += string. 3a. If the string contains attributes with prefixes, such as '<manifest:file-entry manifest:full-path="Picture.jpg" manifest:media-type="image/jpg"/>' the insertion fails and a syntax error is thrown. 3b. If the strings does not contain attributes with prefixes, such as '<manifest:file-entry full-path="Picture.jpg" media-type="image/jpg"/>' the insertion succeeds (but the result is not what was hoped for). This does work in Firefox and Chrome and all existing child elements of element look just like the string in 3a, including prefixes. 1401922 1 334580 mail 2018-02-25 09:22:19 -0800 Created attachment 334580 insertAdjacentHTML with prefixed attributes, minimal testcase This works in Firefox and Chrome and not Safari. 1445986 2 mail 2018-07-28 09:08:00 -0700 Still present in Technology Preview 61 (Safari 12.0) 1955254 3 ahmad.saleem792 2023-05-13 12:04:39 -0700 Took test and changed it into JSFiddle: https://jsfiddle.net/L9uk0s2p/ *** Chrome Canary 115 *** Nothing in Console *** Safari Technology Preview 169 *** "<a class='gotoLine' href='#45:22'>45:22</a> SyntaxError: The string did not match the expected pattern." *** WebKit ToT (264046@main) *** [Minibrowser] "<a class='gotoLine' href='#45:22'>45:22</a> SyntaxError: The string did not match the expected pattern." *** Firefox Nightly 115 *** "<a class='gotoLine' href='#45:0'>45:0</a> SyntaxError: An invalid or illegal string was specified" _____________________________ From Comment 01, it seems that Firefox also changed the behavior since it was working fine. 1955351 4 annevk 2023-05-15 00:19:51 -0700 This also happens for innerHTML. It seems like we don't implement https://html.spec.whatwg.org/#xml-fragment-parsing-algorithm correctly. Maybe Firefox changed their XML parser recently? 1987017 5 ahmad.saleem792 2023-10-23 17:14:27 -0700 I took additional tests for this from Blink: https://src.chromium.org/viewvc/blink?view=revision&revision=191940 and now trying to merge in PR for fixing bug 66424. 334580 2018-02-25 09:22:19 -0800 2018-02-25 09:22:19 -0800 insertAdjacentHTML with prefixed attributes, minimal testcase insertAdjacentXML.js text/plain 514 mail bGV0IHBhcnNlciA9IG5ldyB3aW5kb3cuRE9NUGFyc2VyKCkKbGV0IHN0cmluZyA9IGA8P3htbCB2 ZXJzaW9uPSIxLjAiPz48Y3A6Y29yZVByb3BlcnRpZXMgeG1sbnM6Y3A9Imh0dHA6Ly9zY2hlbWFz Lm9wZW54bWxmb3JtYXRzLm9yZy9wYWNrYWdlLzIwMDYvbWV0YWRhdGEvY29yZS1wcm9wZXJ0aWVz IiB4bWxuczpkYz0iaHR0cDovL3B1cmwub3JnL2RjL2VsZW1lbnRzLzEuMS8iIHhtbG5zOnhzaT0i aHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEtaW5zdGFuY2UiPjxkYzp0aXRsZT48L2Rj OnRpdGxlPjwvY3A6Y29yZVByb3BlcnRpZXM+YApsZXQgZG9tID0gcGFyc2VyLnBhcnNlRnJvbVN0 cmluZyhzdHJpbmcsICd0ZXh0L3htbCcpCmxldCBlbCA9IGRvbS5xdWVyeVNlbGVjdG9yKCdjb3Jl UHJvcGVydGllcycpCmVsLmluc2VydEFkamFjZW50SFRNTCgnYmVmb3JlZW5kJywnPGRjdGVybXM6 bW9kaWZpZWQgeHNpOnR5cGU9ImRjdGVybXM6VzNDRFRGIj48L2RjdGVybXM6bW9kaWZpZWQ+JykK Cg==