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

[waybar] Can't overwrite default waybar css #559

Closed
nakibrayane opened this issue Sep 18, 2024 · 4 comments
Closed

[waybar] Can't overwrite default waybar css #559

nakibrayane opened this issue Sep 18, 2024 · 4 comments

Comments

@nakibrayane
Copy link

For example, when I use the option:

programs.waybar.style = /* css */ ''
  #workspaces button {
    border: none;
  }
''

My CSS is added at the top of the file $HOME/.config/waybar/style.css before the CSS from stylix. like this:

#workspaces button {
  border: none;
}

@define-color base00 #292828; @define-color base01 #32302f; @define-color base02 #504945; @define-color base03 #665c54;
@define-color base04 #bdae93; @define-color base05 #ddc7a1; @define-color base06 #ebdbb2; @define-color base07 #fbf1c7;

@define-color base08 #ea6962; @define-color base09 #e78a4e; @define-color base0A #d8a657; @define-color base0B #a9b665;
@define-color base0C #89b482; @define-color base0D #7daea3; @define-color base0E #d3869b; @define-color base0F #bd6f3e;

...

#workspaces button {
    border-bottom: 3px solid transparent;
}

...

Which makes my overwrites non functional, and using !important doesn't seem to work.

To solve this issues the custom CSS provided with programs.waybar.style option should be at the bottom of the file $HOME/.config/waybar/style.css after the CSS from stylix.

@trueNAHO
Copy link
Collaborator

Is this is a duplicate issue of #429?

@nakibrayane
Copy link
Author

nakibrayane commented Sep 19, 2024

Is this is a duplicate issue of #429?

This is not the exact solution that I was looking for, but it will solve my problem.

@danth
Copy link
Owner

danth commented Sep 20, 2024

You can use lib.mkBefore / lib.mkAfter to change the order that the option definitions are merged

@nakibrayane
Copy link
Author

You can use lib.mkBefore / lib.mkAfter to change the order that the option definitions are merged

This resolves my issue, Thank you :)

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

3 participants