Chrome after update won't respect system titlebars (KDE)

I was surprised to see the CSD in Chrome, instead SSD (titlebar) generated by kwin. I checked the settings, and they stayed the same. Turning them on or off doesn’t change anything, unlike earlier, where it was turning titlebar on/off.

Is it just the issue on my side, or something general?

EDIT: Found on AUR page that disabling flag use-ozone-platform in chrome://flags helps.
It turned out to be a workaround, because it disables the CSD feature completely, so it forces SSD titlebar anyway. It works for me, but is not an end solution, where the feature should work as before.

Chrome 94 now supports CSD:
Chrome 94 now supports CSD properly:

1 Like

It always supported it :confused:
Looks like the only change is that they broke the CSD/SSD switcher, and now it forces CSD despite if it’s on or off.

1 Like

As the article says, it now supports CSD properly; at least for GTK.

Disabling ozone is not a viable long-term solution because ozone is Chromium’s new graphics platform on Linux. The old platform will be removed in a release in the near future.

Edit: Has anyone reported this to

True, but the issue showed up this week, while this proper CSD solution showed at least a month earlier, so the bug must be recent.

No, not so far. Maybe when I find time, but that’s always a problem. But first, I would have to install Chromium to see if the bug happens there as well. If not, then maybe it’s Arch’s compilation issue?

OK, I checked chromium and…

  1. it launches with titlebar
  2. it has no option to enable/disable system titlebar
  3. when flags are checked, ozon status is DEFAULT and yet it behaves as it was not enabled
  4. when I switched it to enabled, titlebar changed to CSD, option showed up and the same issue happens - no matter what setting, CSD is always forced

So yeah, it looks like the source of a bug is Chromium itself.
Since there are many Plasma users, someone had to submit that bug already, at least that is what I suspect. However, I couldn’t find anything related.

OK, I submitted the bug: