I suppose I must have a blind spot in my web programming knowledge. I see sentences like this:
The problem that prevented us from using the HTML5 parser for about:blank is that a bunch of test cases assume that when about:blank is parsed from a stream, the whole operation happens as a single event loop task.
Why do you need an HTML parser to render nothing? Gecko's test cases? Then why don't they fix the test cases?
This is OK for parsing streams from the network...However, it was a major problem with data: URLs in test cases and it still is a problem with about:blank in test cases.
Why?
[lots of stuff]
Why does this matter? about:blank is blank, right? "initially create the DOM of about:blank there synchronously?" What DOM? Is there some meaningful takeaway from this article besides "the Firefox codebase is twisted up" and the ancillary "different browsers handle iframes and new windows with different threading models?"
EDIT: Oh, OK. rwmj's comment above helped explain. I deleted my parent comment, which may have been unfair, then.
The problem that prevented us from using the HTML5 parser for about:blank is that a bunch of test cases assume that when about:blank is parsed from a stream, the whole operation happens as a single event loop task.
Why do you need an HTML parser to render nothing? Gecko's test cases? Then why don't they fix the test cases?
This is OK for parsing streams from the network...However, it was a major problem with data: URLs in test cases and it still is a problem with about:blank in test cases.
Why?
[lots of stuff]
Why does this matter? about:blank is blank, right? "initially create the DOM of about:blank there synchronously?" What DOM? Is there some meaningful takeaway from this article besides "the Firefox codebase is twisted up" and the ancillary "different browsers handle iframes and new windows with different threading models?"
EDIT: Oh, OK. rwmj's comment above helped explain. I deleted my parent comment, which may have been unfair, then.