Platform/HTML5 parser tasks: Difference between revisions
< Platform
Jump to navigation
Jump to search
(→Things that need to be done before turning the HTML5 parser on by default: Mochitest to zarro!) |
|||
| Line 9: | Line 9: | ||
**This will either be simple or so rare that it's not an alpha blocker after all. | **This will either be simple or so rare that it's not an alpha blocker after all. | ||
**Need to reproduce this with debugger attached. | **Need to reproduce this with debugger attached. | ||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=281241 281241] introduced a new reftest that doesn't pass when the HTML5 parsing algorithm is in use, because the DOM is different. | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=546381 546381] browser_bug537449.js fails | |||
**The connection to HTML parsing is unclear. | |||
**Requested help from dtownsend who is the author of the test case. | |||
*The following are waiting for landings by others | *The following are waiting for landings by others | ||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=534458 534458] test failure on css3.info selectors test with :checked{} | **[https://bugzilla.mozilla.org/show_bug.cgi?id=534458 534458] test failure on css3.info selectors test with :checked{} | ||
Revision as of 08:05, 10 March 2010
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
- Get reviews on hsivonen's pending patches. (various people)
- 536097 spinning in nsHtml5TreeBuilder::startTag()? (hsivonen)
- This will either be simple or so rare that it's not an alpha blocker after all.
- Need to reproduce this with debugger attached.
- 281241 introduced a new reftest that doesn't pass when the HTML5 parsing algorithm is in use, because the DOM is different.
- 546381 browser_bug537449.js fails
- The connection to HTML parsing is unclear.
- Requested help from dtownsend who is the author of the test case.
- The following are waiting for landings by others
- 534458 test failure on css3.info selectors test with :checked{}
- Waiting on lazy frame construction from Timothy Nikkel. (Seems reviewed and waiting landing.)
- 543726 dom/tests/mochitest/ajax/offline/test_foreign.html fails
- honzab has a fix. Waiting for review.
- 534458 test failure on css3.info selectors test with :checked{}
- Update the html5lib test suite snapshot used by mochitest. (jgriffin)
- Review the unreviewed parser core code. (sicking)
- Create a "slow tp" test suite for exercising speculative parsing. (bnewman) What if this suite reveals something bad?
- Security review.
Things that need to happen before shipping the HTML5 parser in a final Firefox release
- Fix "[HTML5]" bugs marked P2. (hsivonen)