254
edits
Platform/HTML5 parser tasks: Difference between revisions
Jump to navigation
Jump to search
m
→Things that need to be done before turning the HTML5 parser on by default
| Line 10: | Line 10: | ||
**This bug has a patch that papers over the problem. However, this patch didn't pass review, because it doesn't fix waitForFocus code. Attempts to fix the library code without making other tests fail have been unsuccessful. | **This bug has a patch that papers over the problem. However, this patch didn't pass review, because it doesn't fix waitForFocus code. Attempts to fix the library code without making other tests fail have been unsuccessful. | ||
**On the high level, the problem is that when XUL (as opposed to Web content) does window.open, it looks like it's undetectable from JS immediately afterwards if the window intends to load about:blank and is done loading or if it intends to navigate to another URL when the event loop gets a chance to spin. | **On the high level, the problem is that when XUL (as opposed to Web content) does window.open, it looks like it's undetectable from JS immediately afterwards if the window intends to load about:blank and is done loading or if it intends to navigate to another URL when the event loop gets a chance to spin. | ||
**Waiting | **Waiting for advice on how to proceed. | ||
**''Time estimate'': Week to two weeks (overlapping with other work). A fix to the SimpleTest library may affect other test cases, which may result in having to adjust a yet unknown number of test cases. It's so far unknown if the SimpleTest library is fixable without changing Gecko. | **''Time estimate'': Week to two weeks (overlapping with other work). A fix to the SimpleTest library may affect other test cases, which may result in having to adjust a yet unknown number of test cases. It's so far unknown if the SimpleTest library is fixable without changing Gecko. | ||
*The following are waiting for landings by others | *The following are waiting for landings by others | ||