It appears that the View Selection Source feature serializes the selection and then feeds the serialization to the parser. This is inefficient and has undesirable side effects when the new parser highlights the lack of doctype as an error. Instead, there should be a DOM-to-DOM conversion of the selection into a document that looks right with viewsource.css.
Is this in any way affected by new parser from bug 482921?
This bug remains. However, what comment 0 says about highlighting the lack of doctype now shows.
I would assume this is really a "View Source" bug rather than a bug with the serialization of the DOM itself, if View Source is using the wrong method to "serialize" things to begin with... :-)
Component: Serializers → View Source
Product: Core → Toolkit
You need to log in before you can comment on or make changes to this bug.