Closed
Bug 218947
Opened 21 years ago
Closed 19 years ago
button to restart browser after an extension is installed
Categories
(Toolkit :: Add-ons Manager, enhancement)
Tracking
()
RESOLVED
FIXED
mozilla1.8.1alpha2
People
(Reporter: travis.hardiman+bugzilla, Assigned: robert.strong.bugs)
References
()
Details
(Keywords: fixed1.8.1)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030819 Mozilla Firebird/0.6.1+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030819 Mozilla Firebird/0.6.1+
It would be nice if there was some easy way to restart the browser after
installing an extension. Especially if it was just a button in the toolbar. If
it would retain the current tabset it would be simply amazing.
Reproducible: Always
Steps to Reproduce:
1. Install any extension
2.
3.
Actual Results:
i had to bookmark my tabs, close the browser, open the browser, open the
bookmarks for the tabs, delete the bookmarks for the tabs
Expected Results:
have a button that does all that in one click
Is there an easy way that I could just write an exension (yes, I see the irony)
that would do this?
Comment 1•21 years ago
|
||
I suppose the idea is that you don't install things on the fly quite like this.
Maybe some people do? Writing an extension to do this would probably be harder
than writing a patch for Firebird, since you'd need to modify how the home page
function would work (or do some copying in/out of values during the unload/load
process)
Of course, this wouldn't address partially filled in forms, etc, since
persisting that data just isn't worth it. If what you're doing can't be
interrupted, unless you desperately need that extension for what you're doing,
wait until you're finished.
Still, its a valid RFE, adding helpwanted in case people are looking for stuff
to hack on.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: helpwanted
Summary: feature request:: button to restart browser after an extension is installed → button to restart browser after an extension is installed
Updated•21 years ago
|
QA Contact: asa
Comment 2•20 years ago
|
||
*** Bug 247037 has been marked as a duplicate of this bug. ***
Comment 3•20 years ago
|
||
*** Bug 252737 has been marked as a duplicate of this bug. ***
Comment 4•20 years ago
|
||
This might be a usability win for extensions. If we don't already have
sufficient strings for this, we'd want to get them in before the l10n freeze
Flags: blocking-aviary1.0PR?
Comment 5•20 years ago
|
||
We should probably save the state of the browser and reopen all the same tabs
which are open.
Comment 6•20 years ago
|
||
Unfortunately this is a bit of a challenge. Later.
Flags: blocking-aviary1.0PR? → blocking-aviary1.0PR-
This is the solution I ended up going with.
http://forums.mozillazine.org/viewtopic.php?t=29529
It seems to work well enough for me, but I could understand someone's confusion
after filling out a long form and having those values not persist.
Comment 8•20 years ago
|
||
I'd like to suggest that, after searching for updates to extensions (in both
Firefox, Mozilla, and Thunderbird) and the upgrade requires a restart, the user
be prompted to restart the application, which will then close and then re-load
the application. I don't consider it that important that the application
re-start in the same state that it was when it was shut down to upgrade the
extension but it would be nice either to be prompted to restart or have a button
(or menu item) to restart the browser. A button/menu item to restart would also
come in handy when plug-ins crash (as Adobe Acrobat tends to do from time to
time) -- it doesn't bring down the browser but suggests that the browser be
restarted.
Comment 9•20 years ago
|
||
*** Bug 220026 has been marked as a duplicate of this bug. ***
Comment 10•19 years ago
|
||
The new Update mechanism (Help / Check for Updates...) in the recent Deer Park
builds has a button marked "Restart Deer Park Now". It appears to match the
request of the original bugposter, with the exception of saving the current
tabset. Would it be possible to use the same code to patch this bug?
Updated•19 years ago
|
Flags: blocking-aviary1.1?
Comment 11•19 years ago
|
||
Might get fixed anyway, but saving state information is tricky.
Flags: blocking-aviary1.1? → blocking-aviary1.1-
Comment 12•19 years ago
|
||
(In reply to comment #11)
> Might get fixed anyway, but saving state information is tricky.
Should the "saving state information" part of this bug be duped to Bug 159357
(Add "Last tabs visited" to Navigator startup preferences / save tab session
when closing, quitting), leaving only the EM restart button for this bug?
Comment 13•19 years ago
|
||
I agree to comment 8 that FF should ask whether it should restart now or
manually later just like windows asks the user.
But i think this will have to wait until session saving is implemented.
Comment 14•19 years ago
|
||
There's now an extension that does this, Restart Firefox (only works with 1.5):
http://forums.mozillazine.org/viewtopic.php?t=319438
SessionSaver can be used to save and reload tabs after the restart.
Comment 15•19 years ago
|
||
The part about saving the tabs during an exit/restart can be done via the SessionSaver extension (https://addons.mozilla.org/extensions/moreinfo.php?id=436). It will not only save your tabs, but will also save your inputs in form fields and textareas. Combine this with the previously mentioned RestartFirefox extension and you've got your functionality.
Assignee | ||
Comment 16•19 years ago
|
||
This is being added in bug 329045
Assignee: firefox → nobody
Component: General → Extension/Theme Manager
Depends on: 329045
QA Contact: extension.manager
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → robert.bugzilla
Assignee | ||
Comment 17•19 years ago
|
||
Fixed by the checkin of bug 329045. The metabug for Session Restore is Bug 328154 and that will be added for the EM after Session Restore lands
Assignee | ||
Updated•19 years ago
|
Target Milestone: --- → Firefox 2 alpha2
Assignee | ||
Updated•19 years ago
|
Keywords: fixed1.8.1
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•