598267 - Handle stalled tabs in some fashion for cascaded restore

Status: NEW

(Firefox :: Session Restore, defect)

Description

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

Right now we don't handle stalled tabs at all. So we could get stuck loading a couple tabs and the rest of the session remains unloaded.

tabbrowser does this with a simple setTimeout, so we could do something like that...
http://mxr.mozilla.org/mozilla-central/source/browser/base/content/tabbrowser.xml#573

Comment 1

[(no longer active)]

Is there a good reason that this blocks betaN?  If not, it should be moved over to final+.

(The fact that johnath retargetted this for betaN on Dec 15 tells me that there is a good reason, it just wasn't mentioned here.)

Comment 2

[Dietrich Ayala (:dietrich)]

Session restore changes are historically regression prone, we should keep it betaN+.

Comment 3

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

Agreed on keeping it betaN.

If this ends up getting blocking-'ed, I think we should look at working on this for .x. Or just 5.

I haven't noticed any complaints and we'll load other tabs as selected even if one gets stalled. So in case somebody wants to make this a [hardblocker], I don't think we need to.

Comment 4

[Mike Beltzner [:beltzner, not reading bugmail]]

** PRODUCT DRIVERS PLEASE NOTE **

This bug is one of 19 being moved from blocking2.0:betaN+ to blocking2.0:- as we reached the endgame of Firefox 4. The rationale for the move is:

 - the bug had been identified as a "soft" blocker which could be fixed in some follow up release
 - the bug had been identified as one requiring beta coverage, thus is not appropriate for a ".x" stability & security release

The owner of the bug may wish to renominate for .x consideration.

Comment 5

[Mike Beltzner [:beltzner, not reading bugmail]]

(er updating flag to "-" as per previous comment!)

Comment 6

[Paul O'Shannessy [:zpao] (not bugmail, email directly)]

Nearly 2 years later and this hasn't become an issue.