-
-
Notifications
You must be signed in to change notification settings - Fork 750
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
No Text Highlight Upon Workspace Buttons #3041
Comments
I have a similar issue and suspect that they're the same cause (please let me know if a separate issue is best). #workspaces button {
padding: 0 5px;
background-color: transparent;
color: #ffffff;
border-bottom: 3px solid transparent;
}
#workspaces button.visible {
border-bottom: 3px solid #ffffff;
} With waybar 0.10.0, visible workspaces don't have the last style applied to them; they look just like inactive workspaces. |
Can confirm. Waybar |
|
When I run There is however |
I can confirm that this is fixed for me on |
Can also confirmed it is fixed on |
I second this. If even after that release this bug manifests again, anyone else can just reopen this, since it's a feature that can be easily overlooked during testing, it seems. |
It's confirmed for https://github.com/Alexays/Waybar/tree/0.10.2 to have solved this. Anyone is free to reopen this should it crop up again. Closing this for now |
It appears that when work underwent for #2998, there were some highlighting bugs, including this one #2998 (comment), which was promptly fixed at grimpy@7b3d155
However, I have discovered another bug that went unnoticed:
Workspace text highlighting for focused workspace in
0.9.24
Workspace text highlighting for focused workspace in
0.10.0
Relevant
style.css
code is as follows, and is confirmed to be working in0.9.24
, but not anymore in0.10.0
:Hence, on
0.10.0
, text highlighting seems broken for focused and urgent workspace states upon workspace buttons, regardless of workspace button non-text highlighting state.Workspace highlighting as described in #2998 (comment) indeed was fixed, but not text highlighting, presumably since not many users actually rely on text highlighting, thus the bug went unnoticed.
The text was updated successfully, but these errors were encountered: