-
Notifications
You must be signed in to change notification settings - Fork 970
button style inconsistency on about:preferences (button normalization) #9223
Comments
Another thing we have to decide: should we revert That would make the size of the buttons on about:preferences#sync same as the other buttons on other preference tabs. @cezaraugusto I noticed that font-weight: 500 has not been specified to The reason why "Done" button on bookmark hanger looks bold is due to font-family chosen there; the font-family specified for the button is itself bolder than the font-family for the buttons on preferences, so the effect is not intentional but coincidental. If we normalize the font-family, the done button could look thinner, based on the font-family we would choose. |
we need to get them all referencing the same style definition so we can easily refine it collectively. I want to flatten them out a bit and reduce the shadows. So in this case, sync is "out of sync". : ) |
browser-laptop/less/window.less Line 9 in 734cefc
|
The cause of the difference is that, while on about pages |
Describe the issue you encountered: the button style on
about:preferences#sync
is different with that on the other tabs ofabout:preferences
such asabout:preferences#payments
The button on the left looks thinner and the font-size looks smaller than the button on the right.
See:
browser-laptop/less/button.less
Line 160 in 548e11b
Also the styles of buttons on browser's UI such as bookmark hanger dialog is different with them.
See:
browser-laptop/less/window.less
Line 9 in 734cefc
You would see the different font-family is specified to each of them.
We are on the way of normalizing the buttons by converting
buttton
component withbrowserButton
component. We would have to investigate whichfont-size
,font-family
, andline-height
(the properties which can/must be specified withfont
property) should be applied as tobrowserButton
insidebrowserButton.js
.Brave Version (revision SHA): 0.15.314
Extra QA steps:
1.
2.
3.
Any related issues:
The text was updated successfully, but these errors were encountered: