-
-
Notifications
You must be signed in to change notification settings - Fork 423
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
buffer: Review status buffer style. #3228
Conversation
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.
Thank you andre,
As far as I can tell -- this is what was proposed. I have not had a chance to see it with John out sick and no screenshots, but I can see that you made some changes to the styling and I trust you totally in this.
abce1d9
to
8efec46
Compare
No need to rush since this is not a priority. You and @jmercouris should take a look together and make a decision. I've just changed something now, while taking a second look. See the recording below. simplescreenrecorder-2023-10-20_10.12.33.mp4 |
Looks grand. Will review with John when able. |
Uniformize hover and active CSS pseudo classes across all interactive UI elements. Make use of new theme color and ditch opacity hacks. Review tabs UI.
Status buffer was switched to flexbox, columns were from grid.
36dbf03
to
f1ab2de
Compare
I did a rebase since each commit was atomic. |
Verdict about selected tab background-color still out, but we will get to it. |
All good. I'd rather have a single commit for such small changes. The authorship of the commit is rather unimportant in my view. Thanks. |
Description
Uniformize hover and active CSS pseudo classes across all interactive UI elements.
Make use of new theme color and ditch opacity hacks.
Review tabs UI.
Closes #3142.
Discussion
Currently it's a draft to close the mentioned issue. @jmercouris please demo it with @lansingthomas and make any necessary changes.
Checklist:
Everything in this checklist is required for each PR. Please do not approve a PR that does not have all of these items.
:documentation
s written in the aforementioned style. (It's OK to skip the docstring for really trivial parts.)changelog.lisp
with my changes if it's anything user-facing (new features, important bug fix, compatibility breakage).migration.lisp
entry for all compatibility-breaking changes.