https://bugs.kde.org/show_bug.cgi?id=478556
--- Comment #85 from Zamundaaa <xaver.h...@gmail.com> --- (In reply to Oded Arbel from comment #84) > Firefox upstream just applied a "workaround" (their definition) to fix this > issue by updating the input region. Afaiu GTK is doing something wrong, so that seems fine. > A. do we know that the issue with input region being set incorrectly by the > window (and or not updated on resize) isn't what the IntelliJ issue is about? I'm relatively sure that's not possible; Xwayland doesn't set any input regions (yet), so it always covers the whole window for X11 apps on Wayland. > B. IIUC, shaping the input region is related to non-rectangular windows, > i.e. windows with transparent parts where the surface will not receive > events on those transparent areas - isn't the Firefox issue flies in the > face of Wayland security assurances? If windows can decide not to receive > events on areas they paint (and let them "fall through" to the next window) > it sounds like they can also grab events on areas that they don't paint by > shaping their input region to be larger than the painted region - this seems > problematic to me. Apps don't get input events outside of the input region. There's no grabbing input events on Wayland. -- You are receiving this mail because: You are watching all bug changes.