Closed
Bug 1401956
Opened 8 years ago
Closed 8 years ago
Browser restart required after upgrading to the latest “Grammarly For Firefox” version
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
INVALID
People
(Reporter: vtamas, Unassigned)
References
Details
Attachments
(1 file)
1.36 MB,
image/gif
|
Details |
[Affected versions]:
Firefox 57.0a1 (20170920220431)
Firefox 56 RC (20170918210324)
Firefox 55.0.3 (20170824053622)
[Affected platforms]:
Windows 10 64-bit
Mac OS X 10.12.3
[Steps to reproduce]:
1.Launch Firefox with a clean profile.
2.Install the following webextension version: https://addons.mozilla.org/firefox/downloads/file/668017/grammarly_for_firefox-8.769.994-an+fx.xpi?src=version-history
3.Go to Add-ons Manager -> Extensions and check for updates.
4.Reload the page after the new version is downloaded.
[Expected Results]:
The webextension is automatically updated to the latest version and there is no restart required.
[Actual Results]:
- A browser restart is required in order to complete the upgrade.
- See attached screencast.
Comment 1•8 years ago
|
||
This extension uses browser.runtime.onUpdateAvailable to defer the update. From a quick glance at the code, I'm not sure what they're trying to achieve by deferring it, but there's no Firefox bug here.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Comment 2•8 years ago
|
||
Problem is that Firefox need to be restarted, which is nearly like in legacy non e10s extension era. Now, every WebExtension, even old legacy extension, with e10s compatibility are not need to Firefox to be restarted, when extension was updated to newer version. So I think it's clearly the bug there.
Flags: needinfo?(aswan)
Comment 3•8 years ago
|
||
I'm not sure what to add beyond comment 1. A webextension can choose to defer updates until the next restart and that's what grammarly is doing. I have no idea why grammarly chooses to do that, but feel free to ask the extension author.
Flags: needinfo?(aswan)
You need to log in
before you can comment on or make changes to this bug.
Description
•