Home

I mean many Wayland compositors is kinda like old browsers at the moment. They all implement a common spec and then implement a bunch of their own extensions to get features the spec doesn’t allow for. And apps have to be aware of these custom extensions to make use of them. So in the KDE case, I imagine a lot of their apps are aware of KDEs own extensions to Wayland. But it doesn’t mean all of them are.

Surely it’d be absurd for each individual app to need to implement this spec - that defeats the whole point. I can believe it’d be down to Qt or some other library, but as I said, I’m sure that’d apply to those two apps.

Yeah, I imagine there’s some QT bits for implementing a lot of it, if it detects them being available. Not being massively familiar with QT or how those two apps make use of it, I can’t assume they’d be making use of the components that’d implement KDEs custom extensions. So you know shrugs