Platform/HTML5 parser tasks: Difference between revisions

Platform/HTML5 parser tasks (view source)

Revision as of 14:34, 17 March 2010

1,490 bytes added , 17 March 2010

→‎Things that need to be done before shipping the HTML5 parser in a final Firefox release: Fill in time estimates

Hsivonen

254

edits

@@ Line 31: / Line 31: @@
 * 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
+***''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=482917 482917] Make HTML5 parsing not regress stream data availability to extensions
+***''Time estimate'': Couple of days (if Google Desktop no longer needs this functionality) to unknown (if an alternative needs to be designed together with Google Desktop engineering)
 ** [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=537948 537948] The procedure to fix a <a> around a <tr> element is acting weird.
+***''Time estimate'': Less than a day to discover if this is a parser bug or a spec bug. If this is a spec bug, the time it takes to get a spec fix is unknown.
 ** [https://bugzilla.mozilla.org/show_bug.cgi?id=539210 539210] Revise the translator README to cover all makefile functionality
+***''Time estimate'': Less than a day.
 ** [https://bugzilla.mozilla.org/show_bug.cgi?id=539434 539434] The translator isn't updating parser/html/javasrc/
+***''Time estimate'': Less than a day.
 ** [https://bugzilla.mozilla.org/show_bug.cgi?id=540480 540480] [Evang?] Hootsuite.com dashboard not loading with HTML5 parser turned on
-** [https://bugzilla.mozilla.org/show_bug.cgi?id=542104 542104] Page doesn't load with HTML5.enabled;true and a modified UA string
+***''Time estimate'': For the time being, I'm treating this as a probable evangelism issue. Site contacted. No idea if/when they react.
 ** [https://bugzilla.mozilla.org/show_bug.cgi?id=548232 548232] Fix the caching of document.written meta charset on wyciwyg channel
+***''Time estimate'': Unknown. Probably over a week. This one needs multi-vendor email discussion on the WHATWG list in order to decide what the desired fix should be.
 ** [https://bugzilla.mozilla.org/show_bug.cgi?id=548767 548767] Make sure <script for> behaves right
+***''Time estimate'': In theory less than a day, but my intuition says this one won't be quite without problems, so I'm guessing it'll need some follow on another day, too. (Also, need to decide whether to keep current code or whether to reimplement the spec that will have changed to say what the WebKit devs reverse engineered from Gecko.)
 ** [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.
 *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