I was able to open native Chrome or Chromium windows with those commands:
$ google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland
or
$ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
After that, Chromium or Chrome behaved exactly as Firefox, namely, all links clicked from external apps (Thunderbird, Libre Office Writer) didn’t raise to the foreground, only were alerted (blinked red, in my case).
This answers the question and makes clear that this is a Wayland limitation.
Where do I report Wayland issues?
For those interested in checking it:
- Open a browser (any browser) as native Wayland window.
- Check with Kwin debug console if it’s really a Wayland one.
- Open Thunderbird or Libre Office Writer with links, click on them.
Kwin debug console opens with this command:
dbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole
Again, a browser must be already opened and in Wayland mode.
In many tests, this was replicable 100%.
Also, see the site:
and note the @Shawn’s comment:
"Wondering why links in external applications wont launch when wayland is set in Chromium. Clicking a link in email or dolphin flashes the icon orange if the browser is open and/or minified.
This doesn’t occur when X11 is set in Chromium, just wayland."
Doesn’t it remind you my exact issue?