Removed Firefox View button returns after restart
Categories
(Firefox :: Firefox View, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox133 | --- | unaffected |
firefox134 | --- | unaffected |
firefox135 | + | verified |
firefox136 | --- | verified |
People
(Reporter: gwarser, Assigned: nsharpley)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-sidebar])
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
- right click on the Firefox View button and select "Remove from Toolbar" or click "Customize Toolbar..." and drag the button out
- restart the browser
Actual results:
The button is back on the Toolbar
Expected results:
It should be hidden
Comment 1•8 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Firefox View' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
![]() |
||
Comment 2•8 months ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c989b7bd05b81c0072bd2621c6b92c3aa9618b4f&tochange=d6d0fbdef190091e5dac0c7fe409befc4c95bd36
Comment 3•8 months ago
|
||
:nsharpley, since you are the author of the regressor, bug 1926360, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•8 months ago
|
Comment 4•8 months ago
|
||
The bug is marked as tracked for firefox135 (nightly). However, the bug still isn't assigned.
:pluk, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Comment 6•8 months ago
|
||
Updated•8 months ago
|
Updated•8 months ago
|
Comment 11•8 months ago
|
||
bugherder |
Updated•7 months ago
|
Comment 12•6 months ago
|
||
I was able to reproduce it on Win11x64 using FF build 135.0a1(20241209213901).
Verified as fixed on Win11x64/Ubuntu22.04 using FF build 136.0a1 and 135.0b4.
Description
•