Open
Bug 1234069
Opened 9 years ago
Updated 2 years ago
'Block plugin' button is absent in Private Mode, and plugins settings be passed to normal mode
Categories
(Firefox :: Private Browsing, defect)
Tracking
()
NEW
People
(Reporter: kuroptev, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
46.43 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20151216175450 Steps to reproduce: Start Firefox in normal mode. Start an additional private window using Ctrl+Shift+P. In the private windows visit a webpage with some click-to-play plugin, like Speedtest.net with Flash (I have Flash in Ask mode). Enable a plugin using "Allow Now" option of plugin indicator in the Location Bar. Actual results: Plugin is enabled, but now there is no "Block plugin" option to call using plugin indicator in the Location Bar, as it was before 43.0.1 update. Moreover, if the private windows is closed and new one is reopened, the plugin will be enabled for Speedtest.net website, despite the default option for the plugin is Ask. So, not only "Block Plugin" button is lost after 43.0.1 update, but Private Window mode persist plugin setting between sessions. Expected results: There must be "Block Plugin" button in Private mode, as it was before update, and as it still is in normal mode. See picture attached.
Updated•9 years ago
|
Component: Untriaged → Private Browsing
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: 'Block plugin' button is absent in Private Mode → 'Block plugin' button is absent in Private Mode, and plugins settings be passed to normal mode
Comment 1•8 years ago
|
||
This bug is essentially a dupe of bug 892487. The tradeoff between losing the block action and the privacy leak was well understood in bug 891116 and the lesser of two evils was chosen. I'm not marking it as a dupe right now, because I think its subject will be useful to others who may try to file the same issue, but I expect this to be fixed once bug 892487 is done.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•