-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group and scope the findbar rules using CSS nesting #18568
Conversation
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @timvandermeij received. Current queue size: 0 Live output at: http://54.241.84.105:8877/8ad2c1f7d669cf4/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/8ad2c1f7d669cf4/output.txt Total script time: 1.03 mins Published |
/botio integrationtest |
From: Bot.io (Linux m4)ReceivedCommand cmd_integrationtest from @timvandermeij received. Current queue size: 0 Live output at: http://54.241.84.105:8877/a99fa62fe79c1ac/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_integrationtest from @timvandermeij received. Current queue size: 0 Live output at: http://54.193.163.58:8877/ffc9debbfff0603/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/a99fa62fe79c1ac/output.txt Total script time: 8.49 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.193.163.58:8877/ffc9debbfff0603/output.txt Total script time: 19.05 mins
|
cd14b89
to
d8705c1
Compare
d8705c1
to
0f809a6
Compare
The findbar CSS rules predate the general availability of CSS nesting, which makes them more difficult to understand and change safely. The primary issues are that the findbar rules are spread all over the `viewer.css` file, they share blocks with non-findbar elements and the scope of the rules is sometimes bigger than necessary. This refactoring groups all findbar-related CSS rules together, scoped to the top-level `#findbar` element, for improved overview and isolation. Note that this patch only intends to move the existing rules around and not change any behavior yet, but it does lay the foundation for e.g. making the findbar respect the `browser.uidensity` preference in Firefox in follow-up work. Co-authored-by: Calixte Denizet <calixte.denizet@gmail.com>
0f809a6
to
1fcdced
Compare
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @timvandermeij received. Current queue size: 0 Live output at: http://54.241.84.105:8877/c5133c705aaff0e/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/c5133c705aaff0e/output.txt Total script time: 1.03 mins Published |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me, thank you.
The findbar CSS rules predate the general availability of CSS nesting, which makes them more difficult to understand and change safely. The primary issues are that the findbar rules are spread all over the
viewer.css
file, they share blocks with non-findbar elements and the scope of the rules is sometimes bigger than necessary.This refactoring groups all findbar-related CSS rules together, scoped to the top-level
#findbar
element, for improved overview and isolation. Note that this patch only intends to move the existing rules around and not change any behavior yet, but it does lay the foundation for e.g. making the findbar respect thebrowser.uidensity
preference in Firefox in follow-up work.Notes for the reviewer:
#findbar
rules in a different part of the file to make the diff easier. Now the deletions and additions can more easily be compared side-by-side while otherwise they would be intertwined.#findbar
element and noticing that the rules in this block are already inactive:Extracts a part of #18385.