allow in private browsing panel does not work in perma-private browsing
Categories
(Toolkit :: Add-ons Manager, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox76 | --- | unaffected |
firefox77 | --- | unaffected |
firefox78 | --- | verified |
People
(Reporter: kernp25, Assigned: emmamalysz)
References
(Regression)
Details
(Keywords: regression)
Attachments
(5 files)
I saw this TypeError in the browser console: can't access property "checked", checkbox is null
My browser version: 78.0a1 (2020-05-10) (64-Bit)
It seems to happen, after you install an add-on.
e.g. https://addons.mozilla.org/firefox/addon/impero-education-prov204/?src=recommended
Comment 4•4 years ago
|
||
Please don't need-info people unless you have a specific question for a person or an urgent problem. We triage bugs on a weekly basis, and will look into them in due time.
Comment 6•4 years ago
|
||
I can reproduce this issue on FF78.0a1 (2020-05-19) and I can also confirm that the checkbox popup "Allow this extension to run in Private Window" is not displayed anymore on the top right side of the screen when installing a new extension.
The error message from browser console is exactly the one attached in the initial screenshot :
"TypeError: can't access property "checked", checkbox is null"
I will also attach a video with the issue and I will try a bisection in order to provide the regression range.
Updated•4 years ago
|
Comment 7•4 years ago
|
||
Comment 8•4 years ago
|
||
I performed a bisection with following results:
2020-05-20T15:37:19: DEBUG : Found commit message:
Bug 1634031, lazy load appmenu and extension notification panel by using a template r=Gijs
Comment 9•4 years ago
|
||
Thanks for the bisect, updating bug flags.
I noticed this bug before when I tried to install an extension on Nightly while in perma-private browsing mode - the doorhanger did not show up.
IMO this is a P1 bug that should be fixed before 78 goes to Beta, but I'll wait until the next triage meeting before assigning severity.
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
Given it doesn't prevent install, I wouldn't put it to S1. Given there is a patch, P1.
Updated•4 years ago
|
Comment 12•4 years ago
|
||
Comment 13•4 years ago
|
||
bugherder |
Comment 14•4 years ago
|
||
Verified as fixed in latest Nightly(78.0a1 (2020-05-27) ) on Win10x64 and MacOS 10.15.4
Updated•4 years ago
|
Description
•