https://bugs.kde.org/show_bug.cgi?id=457049
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #2 from Nate Graham <n...@kde.org> ---
>From the linked bug report:
> On the other hand, Chrome's requirement is:
> - first, (in some situations, like PWA), Chrome would like to process keys.
> - If Chrome (incl. app) does not process it, then it would like to send back
> to the system (compositor) to let them process.
That's not acceptable on Wayland, yeah. The explicit design is for the
compositor to be in charge here.
I guess we need to plead our case to the Chromium devs, or somehow work around
it in KWin, if that's even possible.
--
You are receiving this mail because:
You are watching all bug changes.
