While a document is loading, reflow of the previous document is needed until the new document can be displayed. In more detail: 1) When the home page is loading (for those who have NGLAYOUT_HOME set to a non- local file), the viewer window should fill with something - probably white (or gray, if that is the default BG color). 2) When the window is resized or brought to the front while a document is loading, there is nothing displayed in the middle of the window, leaving whatever was there before. Drawing a blank screen would be better than what you do now, but you probably should draw the previous document, and allow movement within it (and allow clicking on a link to cancel the load in progress and start a new one). This would make NGLayout feel much more like a browser...

P1 bugs are reserved for crashes.

Setting all current Open/Normal to M4.

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

Accepting bug...

Setting milestone to M8...

Moving non-crashing layout and webshell component bugs to M8... I already have enough blockers and crashers for M6. If I fix them in time for M6, I'll move some of these bugs back to the M6 milestone. I'm keeping the M7 milestone for fixing XML bugs.

David, is the situation better now with incremental reflow enabled. I see content on the page reasonably fast when I click on a link to load a new document. Do you have any test cases that you can post to this bug report that take an unacceptable time to display? Thanks.

Updating summary to reflect that this is a feature request.

The issue was more about what happens if the document doesn't start loading for a while. This happens to modem users, and the browser should stay responsive and continue to display the old page [4.xP]. (Right now, if I disconnect my modem, apprunner doesn't even try to load a URL because it is unable to load the throbber, and reports an error on that. I'll try and get back to you once Necko lands. Apprunner crashes if I disconnect my modem in the middle of a document load... I'll wait for Necko on that one too.)

Moving out to M10 for now...

Another good test case: http://www.fas.harvard.edu/~dbaron/css/test/sec051103 - try any of the unvisited links. Right now apprunner basically freezes. It should be responsive to clicking on other links, scrolling, :hover, the cursor should change, etc. This is more of a [4.xP] than an [RFE].

I'm on vacation for the next two weeks. Consequently, I'm moving these M10 bugs over to M11...

This is not a beta stopper. Moving out to M15...

This bug is fixed in the latest builds. Specifically, when I go to http://www.fas.harvard.edu/~dbaron/css/test/sec051103 and click on an unvisited link, Mozilla no longer hangs. Marking worksforme.

Things look much better :-).

Marking verified works for me with the Jan 18th.

[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.