Skip to content
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

Incorrect styling in Panel Button in Gnome 47 (with suggested fix) #237

Closed
jakubzet opened this issue Dec 3, 2024 · 1 comment
Closed

Comments

@jakubzet
Copy link

jakubzet commented Dec 3, 2024

After recent update of Gnome, I've noticed that my favorite theme ( 😄 ) has troubles with top panel buttons (as on attached screenshot below).

Screenshot From 2024-12-02 20-04-25

I was able to find out that that the reason of this issue sits in gnome-shell.css file, basically commenting out the following lines resolved the issue (I've hidden all the unnecessary lines for this case):

#panel .panel-button {
  /* border: 0 none transparent; */
}

#panel .panel-button.clock-display .clock {
  /* border: 0 none transparent; */
}

#panel .panel-button.clock-display:active, #panel .panel-button.clock-display:overview, #panel .panel-button.clock-display:checked, #panel .panel-button.clock-display:focus {
  /* box-shadow: inset 0 -2px #248a76 !important; */
}

#panel .panel-button:active, #panel .panel-button:overview, #panel .panel-button:checked, #panel .panel-button:focus {
  /* box-shadow: inset 0 -2px #248a76 !important; */
}

In my case the Panel buttons are looking just fine (look at the screenshots below, after above fix), both for the centered calendar button, as for the other ones. Should I prepare a Pull Request for this update (but with lines removed instead of commented out)? I can do so, yet I wasn't really sure if there aren't any ongoing works in progress :)

fix-1

fix-2

@jakubzet jakubzet changed the title Incorrect styling in Panel Button in Gnome 47 Incorrect styling in Panel Button in Gnome 47 (with suggested fix) Dec 3, 2024
@jakubzet jakubzet reopened this Dec 16, 2024
@jakubzet
Copy link
Author

The error disappeared after latest update of Gnome (47.1.1-165-1-x86_64 to 47.2-166-1-x86_64). Seems that was some bug in the Gnome itself, therefore I'm closing this issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant