Confirmed users
596
edits
Platform/HTML5 parser tasks: Difference between revisions
Undo spam
(Replaced content with 'When all of a sudden six beavers came from Southwest Angry Buzz the forest quailed before the glare. The jar of trees was broken like pigeons singing.') |
(Undo spam) |
||
| Line 1: | Line 1: | ||
This page outlines what needs to be done to 1) enable the HTML5 parser by default on mozilla-central and 2) ship a release with the HTML5 parser enabled by default. | |||
The HTML5 parser has been suitable for dogfooding for over a year and in the past couple of months there have been virtually no new site compat bugs. Thus, the parser is already alpha quality from a user POV but not from a zero test suite regressions POV. | |||
== Things that need to be done before turning the HTML5 parser on by default == | |||
*The following are waiting for landings by others | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=543726 543726] dom/tests/mochitest/ajax/offline/test_foreign.html fails | |||
***honzab has a fix. | |||
***Waiting for review comments getting addressed and super-review. | |||
*Review the unreviewed parser core code. (sicking) | |||
*Land reviewed patches | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=551344 551344] Patches need landing but only after investigating that tryserver problems aren't caused by them once rebased (hsivonen) | |||
== Things that need to be done before shipping the HTML5 parser in a final Firefox release == | |||
* Fix "[HTML5]" bugs marked [https://bugzilla.mozilla.org/buglist.cgi?priority=P2;short_desc=%5bHTML5%5d;field0-0-0=short_desc;query_format=advanced;bug_status=NEW;bug_status=ASSIGNED;short_desc_type=allwordssubstr;type0-0-0=notsubstring;value0-0-0=%5bPatch%5d P2]. (hsivonen) | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=482913 482913] Make sure document.write() order for nested scripts is right | |||
***Waiting for Hixie to respond to feedback about a test case looking broken. | |||
***''Time estimate'': Hixie's test cases for this can be run in less than a day. If something fails, working out what failed, why it failed and if we want to change code, tests or the spec will take multiple email round-trips through the WHATWG list spanning at least a week. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=483209 483209] The HTML5 parser needs limits on internal buffer growth | |||
***''Time estimate'': Less than a day. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=531016 531016] Make sure the namespace optimizations in 'in scope' algorithms is right | |||
***''Time estimate'': Less than a day. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552908 552908] Implement spec changes to SVG </a> and </font> handling | |||
***''Time estimate'': Less than a day, provided that reviewers accept slightly ugly code. (A non-ugly solution would seem to require a dramatic refactoring.) | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html | |||
***''Time estimate'': Less than a day, but waiting for the SVG WG to decide whether to remove this event instead. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=557197 557197] in element content expands to CR and shows up as a non-collapsing space in layout | |||
***''Time estimate'': Less than a day if hacked around in the parser. Unknown if fixed more properly in layout. | |||
*Reviews on existing patches | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=548232 548232] Make meta charset have no effect on document.open()ed documents. (bzbarsky) | |||
*Security review. | |||
** Talked to dveditz about how to do the security review for the HTML5 parser, and it's not clear what the best format for the review would be. But we did decide that it's not something we need to do before turning the parser on by default, but we need to do it before we ship it. --jst | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=544994 544994]Create a "slow tp" test suite for exercising speculative parsing. (bnewman) | |||
** ''What if this suite reveals something bad?'' | |||
==Suspended items that may re-enter the list of release blockers== | |||
* Suspended bugs that were previously P2 | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=482917 482917] Make HTML5 parsing not regress stream data availability to extensions | |||
***There's now a patch but no way to test it. | |||
***Suspended, because there are no known extensions that use the API in question and are compatible with Firefox 3.6. | |||
***''Time estimate'': Unknown. (Need to find an extension that actually uses this. The alternative is writing an extension just for testing.) | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=540480 540480] Hootsuite.com dashboard not loading with HTML5 parser turned on | |||
***Moved over to evangelism. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=537948 537948] The procedure to fix a <a> around a <tr> element is acting weird. | |||
***Spec issue. No indication so far on whether this is a problem for real-world sites. The HTML5 behavior seems well enough aligned with the IE8 behavior. | |||