https://bugs.kde.org/show_bug.cgi?id=513785
--- Comment #2 from [email protected] --- (In reply to David Edmundson from comment #1) > Our priority is portals and improving this experience. > Supporting two methods fragments this, we won't be adding this. I have some issues with portals which would make this a far more attractive option: - portals screenshot API returns a URI, whereas this protocol stores the result directly in a CPU or GPU buffer. That makes this protocol far lower latency than portals. - portals screencast API always requires pipewire usage, forcing devs to pull a big and complex library into their projects. For low-latency screenshots this also isn't a great option as it requires an ongoing permanent screen capture just to have the newest frame available. I'm also pretty worried by the ongoing ecosystem split: With so many compositors planning to implement this protocol, and the current trend of screenshot and accessibility apps seemingly mainly using the protocols ober portals, i can barely find any options for screenshot tools that use portals. So please, i would urge you (KWin/Plasma devs) to carefully consider this before outright denying. -- You are receiving this mail because: You are watching all bug changes.
