Open Bug 594285 Opened 14 years ago Updated 2 years ago

Reload all affected tabs when untrusted connection accepted

Categories

(Firefox :: General, enhancement)

x86_64
Linux
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: era+mozilla, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/10.04 (lucid) Firefox/3.6.8
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/10.04 (lucid) Firefox/3.6.8

I am forwarding this bug which I submitted to Ubuntu Launchpad:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/632967

When Firefox crashes (which is regrettably all too frequently) and is restarted into the saved session, all tabs which were open to a site whose certificate is not permanently accepted will be displaying the "Untrusted Connection" screen.

Once I have gone through the "I Understand The Risks" dance in one of those tabs, all tabs affected by the acceptance of the certificate need to be reloaded by hand (find each, and press ctrl-R).

I would like for all those tabs to reload automatically when the certificate is accepted.

I have taken the habit to not check the "Permanently store this exception" box as a reminder to myself to report problems with certificates. I acknowledge that this is fringe behavior; but I also believe it would be moderately easy to implement the proposed fix.

Reproducible: Always

Steps to Reproduce:
1. Have multiple tabs open to https pages in domains with a temporarily accepted SSL certificate
2. Experience another Firefox crash, or quit and restart.  Restore saved session
3. On one of the Untrusted Connection pages, accept the SSL cert temporarily again
Actual Results:  
The page where you accepted the cert reloads, but the other tabs remain on the Untrusted Connection page

Expected Results:  
Other tabs should reload when their connection is no longer untrusted

I acknowledge that this is wishlist territory.
Severity: trivial → enhancement
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.