Remove unecessary .bookmarks-toolbar rule from widget-overflow and appmenu-popup elements.
Categories
(Firefox :: Toolbars and Customization, task, P3)
Tracking
()
People
(Reporter: Gijs, Unassigned)
References
Details
(Whiteboard: [privacy-panel])
Attachments
(1 file)
(deleted),
image/png
|
Details |
After bug 1562881 the lists at these two selections: https://searchfox.org/mozilla-central/rev/e3fc8f8970491aef14d3212b2d052942f4d29818/browser/themes/shared/customizableui/panelUI.inc.css#141-149,166-172 are out of sync.
We should probably also ensure that the protection popup actually gets the requisite class when the bookmarks toolbar is present.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Erica has worked on popup height before, can you please take a look at this? Thanks!
Comment 2•5 years ago
|
||
The rule at line 166-172 is meant for when the icon/anchor is located in the bookmarks toolbar. For example, the library icon in the image I've attached. As far as I can tell, I'm unable to move the urlbar into the bookmarks toolbar, and since the shield is located inside the urlbar, this rule should never need to apply to the shield or protections popup.
I'll close this as invalid for now, please let me know if I've misunderstood your report.
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Reporter | ||
Comment 4•5 years ago
|
||
(In reply to Erica Wright [:ewright] from comment #2)
The rule at line 166-172 is meant for when the icon/anchor is located in the bookmarks toolbar. For example, the library icon in the image I've attached. As far as I can tell, I'm unable to move the urlbar into the bookmarks toolbar, and since the shield is located inside the urlbar, this rule should never need to apply to the shield or protections popup.
I'll close this as invalid for now, please let me know if I've misunderstood your report.
I think that's fine, but then we should probably remove the widget-overflow and appmenu-popup ones from the .bookmarks-toolbar
set of selectors given that they can never be in that toolbar either, and potentially document what that's doing more clearly in the comment already above it?
Comment 5•5 years ago
|
||
I agree, we can rename this bug for that.
Updated•5 years ago
|
Is this meant for 71? Just double checking.
Comment 7•5 years ago
|
||
(In reply to Liz Henry (:lizzard) from comment #6)
Is this meant for 71? Just double checking.
This is low priority, it doesn't need to be in for 71.
Comment 8•5 years ago
|
||
The priority flag is not set for this bug.
:johannh, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•2 years ago
|
Description
•