this is true, but the browser itself reports that it was unable to identify and install itself by default, in the settings it is by default, but third-party applications open links in Fire Fox
I bet you can add an alternative yourself for chrome for update-alternatives for x-www-browser through some configuration.
Still the application and/or your distro are not compliant with this specifications and they should be fixed (you should have the same issue in GNOME or other DE that complies with XDG specification.
We could workaround this in plasma, but Iβd rather not.
Chrome should be able to set itself but it seems it does not support well Plasma, as on my system chromium thinks its default when it is not.
Maybe the issue is that chrome is installed from flatpak and itβs worth installing the official version from google or will it be the same, donβt know?
By the way, the Plasma Integration extension works in the official version of Google Chrome, but it does not work in the Flatpak version of Google Chrome and in FireFox.
This is expected too.
Flatpack is about process isolation, plasma-browser-extension needs direct communication. It could support flatpack with some efforts.
Mentioning that chrome was installed as a flatpack would have saved us a lot of time.
works with every browser I tried from flatpak in my Neon VM so it should be some missing package or misconfiguration or the βhardware probeβ program.