My reading is that outerHTML 's getter runs the fragment serializing algorithm with the "require well-formed" parameter set to true, and the fragment serializing algorithm specifically produces an XML ...
While working on trying to align WebKit's Element.outerHTML setter with other browsers, I noticed a few issues: WebKit & Blink have logic in the setter to merge with the previous & next Text nodes ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results