Bug 482956 - Edge browser window receives events despite being shown in different position
Summary: Edge browser window receives events despite being shown in different position
Status: RESOLVED DUPLICATE of bug 482687
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: 6.0.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-09 08:53 UTC by Norbert Preining
Modified: 2024-03-09 16:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screencast showing the misbehaviour (974.72 KB, video/mp4)
2024-03-09 08:58 UTC, Norbert Preining
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Norbert Preining 2024-03-09 08:53:35 UTC
SUMMARY

When I move the edge browser window out of the screen to the left, it is drawn as being out of it, but mouse actions are taken as if the windows has not moved out but got stuck with the window left border on the left border of the screen.

Also mouse inputs to the window are misplaced as seen in the second part of the attached video.

The moment I click the mouse, the window pops to its "assumed" (wrong) position.


STEPS TO REPRODUCE
1. move edge browser window out of the left edge
2. click on the frame or somewhere around the position where there can be interaction
3. 

OBSERVED RESULT
Window frame and window content reacts despite the window being in different position

EXPECTED RESULT
Not doing this.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
nvidia graphic card
Comment 1 Norbert Preining 2024-03-09 08:54:23 UTC
I forgot to add an important information: That is an X11 session, not wayland session.
Comment 2 Norbert Preining 2024-03-09 08:58:50 UTC
Created attachment 166780 [details]
Screencast showing the misbehaviour
Comment 3 fanzhuyifan 2024-03-09 16:08:08 UTC

*** This bug has been marked as a duplicate of bug 482687 ***