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 background turns black when Chromium is the only window in the workspace #3840

Closed
Kyuunex opened this issue Dec 21, 2024 · 5 comments
Closed

Comments

@Kyuunex
Copy link

Kyuunex commented Dec 21, 2024

Waybar background turns black when Chromium (Native wayland) is the only window in the workspace

2024-12-21T05:19:28+00:00

2024-12-21T05:19:05+00:00

smart gaps has no effect on this
happens on both sway and hyprland

config.json

style.txt
gh wont let me upload css so i renamed it to txt

@Kyuunex
Copy link
Author

Kyuunex commented Dec 21, 2024

chromium launch flag im using is --ozone-platform=wayland. also it's ungoogled chromium but i doubt it makes a difference.

@909oce
Copy link

909oce commented Dec 22, 2024

im having the same issue, but it has nothing to do with chromium, just whenever i close a window on hyprland it causes a black background. reloading waybar fixes it, but then when i close a window again it happens again.

@msmafra
Copy link

msmafra commented Dec 23, 2024

Waybar background turns black when Chromium (Native wayland) is the only window in the workspace

2024-12-21T05:19:28+00:00

2024-12-21T05:19:05+00:00

smart gaps has no effect on this happens on both sway and hyprland

config.json

style.txt gh wont let me upload css so i renamed it to txt

You have this on your .css file, that would set the bar to black when only using chromium:

window#waybar.chromium {
    background-color: #000000;
    border: none;
}

It doesn't consistently work for me it seems, I tested some months back, it worked with some apps but not others, testing with your full config it doesn't work for me with chromium, firefox etc but works with kitty. Kitty sets its title property to only kitty, the others don't. It must be it. but Why it doesn't work for chromium on my system I dunno.

	class: Io.github.ungoogled_software.ungoogled_chromium
	title: Nova guia - Chromium
	initialClass: Io.github.ungoogled_software.ungoogled_chromium
	initialTitle: Nova guia - Chromium
---
	class: Org.chromium.Chromium
	title: Chromium Docs - Ozone Overview - Chromium
	initialClass: Org.chromium.Chromium
	initialTitle: Chromium Docs - Ozone Overview - Chromium
---
	class: kitty
	title: ~
	initialClass: kitty
	initialTitle: kitty

@Kyuunex
Copy link
Author

Kyuunex commented Dec 23, 2024

Thank you. I dont know how that got there and why i didnt notice it, but removing it fixed the issue. It was probably there for a long time but the issue didn't happen in past.
EDIT: i found how that got there

window#waybar.chromium {
my config is based on the default one and i didnt notice it.

oh well.

@Kyuunex Kyuunex closed this as completed Dec 23, 2024
@msmafra
Copy link

msmafra commented Dec 23, 2024

Thank you. I don't know how that got there and why i didn't notice it, but removing it fixed the issue. It was probably there for a long time but the issue didn't happen in past.

oh well.

It's inconsistent for me with both waybar and waybar-git on Fedora.

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

No branches or pull requests

3 participants