Closed Aleksandra0056 closed 1 year ago
Oh, and put address bar buttons (Padlock button, Shield button, Permissions button, address bar extensions buttons, …) into userChrome.rounding.square_toolbarbutton
entry and not into userChrome.rounding.square_navbarbutton
entry.
I want to avoid being too granular.
I also have to think about backwards compatibility for many users.
What exactly are navbar
and toolbar
?
I plan to keep things the way they are unless absolutely necessary.
So, you are not planning to do that?
Yes. There is no plan yet.
Is your feature request related to a problem?
I'm proposing a splitting the
userChrome.rounding.square_button
to:userChrome.rounding.square_navbarbutton
(buttons in navigation toolbar),userChrome.rounding.square_menubarbutton
(buttons in menu bar),userChrome.rounding.square_toolbarbutton
(buttons in other toolbars),userChrome.rounding.square_dialogbutton
(buttons in print dialogue, settings dialogue, and other dialogues…),userChrome.rounding.square_otherbutton
(buttons in other locations, e.g. about sites, close dialogue buttons, and other buttons…).I want this because I have installed
buttons_on_navbar_classic_appearance.css
from CustomCSSforFx, and I don't like, that these buttons are squared in my navbar, because according to the CustomCSSforFx these buttons should be normally rounded, so I want to follow that.And why I want splitting to five entries and not only two entries? Because I want to have a better control of this, because I don't like square buttons in some places, e.g. I mentioned in navbar, because of CustomCSSforFx.
The solution I'd like
(Written in upper section…)
Screenshots or video
No response
Alternatives I've considered
If the five entries would be too much work, then please split it only to:
userChrome.rounding.square_navbarbutton
,userChrome.rounding.square_toolbarbutton
,userChrome.rounding.square_otherbutton
.Additional context
No response