[META] manifest incognito feature support
Categories
(WebExtensions :: General, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: jgruen, Unassigned)
References
(Depends on 10 open bugs, Blocks 2 open bugs)
Details
(Keywords: meta)
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Updated•7 years ago
|
Comment hidden (abuse-reviewed, advocacy) |
Comment hidden (abuse-reviewed) |
Comment 8•7 years ago
|
||
Updated•6 years ago
|
Comment 9•6 years ago
|
||
Comment 10•6 years ago
|
||
Comment hidden (advocacy) |
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
I'm testing the incognito experience in Beta 67 with my add-ons and I've noticed one issue - Options page of each add-on will load broken (because of the javascript restrictions in API) - I would suggest to remove the "Options" button for add-ons that are not allowed in Private Brosing mode. I don't think there are add-ons that uses pure html Options page :)
Also, I've noticed that add-ons installed from Private Browsing mode are not implicitly allowed in Private mode, maybe that's expected?
Comment 15•6 years ago
|
||
(In reply to juraj.masiar from comment #14)
I'm testing the incognito experience in Beta 67 with my add-ons and I've noticed one issue - Options page of each add-on will load broken (because of the javascript restrictions in API) - I would suggest to remove the "Options" button for add-ons that are not allowed in Private Brosing mode. I don't think there are add-ons that uses pure html Options page :)
Can you add a new bug with steps to reproduce? cc me on it.
Also, I've noticed that add-ons installed from Private Browsing mode are not implicitly allowed in Private mode, maybe that's expected?
That is expected.
Best to not use our tracking bug for conversation. If there's an issue just add a bug, we'll triage it.
Thanks!
Updated•6 years ago
|
Updated•2 years ago
|
Description
•