Closed
Bug 1118289
Opened 10 years ago
Closed 8 years ago
pearl crescent page saver e10s
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: yann.lossouarn, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: addon-compat, Whiteboard: [amo-author-notified]triaged)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150106030201
Steps to reproduce:
Tried to get a page screenshot with Pearl Crescent Page Saver addon AND e10s active on Nightly.
Actual results:
Nothing saved, and error message "Type Error"
Expected results:
A picture file should have been saved
[Tracking Requested - why for this release]:
tracking-e10s:
--- → ?
Keywords: addon-compat
Blocks: e10s-addons
Comment 2•10 years ago
|
||
Reproduced with Nightly 39.0a1 2015-02-26 under Win 7 64-bit.
Status: UNCONFIRMED → NEW
Component: Untriaged → Extension Compatibility
Ever confirmed: true
Comment 6•9 years ago
|
||
Reproduced with Ubuntu 14.04 32-bits. It is e10s specific. It works fine without e10s.
The addon also notifies the user about its incompatibility with e10s.
--
Version 47.0a2
Build ID 20160328004018
Update Channel aurora
User Agent Mozilla/5.0 (X11; Linux i686; rv:47.0) Gecko/20100101 Firefox/47.0
Flags: needinfo?(jorge)
Comment 7•9 years ago
|
||
"It looks like Firefox's multi-process mode (Electrolysis) is turned on. Page Saver is not yet compatible with multi-process mode, so this capture probably will not succeed.
You can disable multi-process mode from the General panel within the Firefox Preferences window."
This message pops up once the toolbar addon is selected.
Updated•8 years ago
|
Whiteboard: [amo-author-notified] → [amo-author-notified]triaged
Updated•8 years ago
|
Comment 9•8 years ago
|
||
We have released Page Saver WE (a reimplementation of this extension using the WebExtensions API):
https://addons.mozilla.org/en-us/firefox/addon/pagesaver-we
We kept the old XUL/XPCOM extension on AMO for now because a lot of people use it and it includes features that are not present (and in some cases not possible) using WebExtensions.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•