[Bug]: BrowserWindow grab region should take precedence over BrowserView draggable region
neobyteUK opened this issue · comments
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a bug report that matches the one I want to file, without success.
Electron Version
19.0.5
What operating system are you using?
Windows
Operating System Version
Windows 10
What arch are you using?
x64
Last Known Working Electron version
No response
Expected Behavior
A BrowserWindow with resizable flag set should always be resizable from its edges.
Actual Behavior
A BrowserView with '-webkit-app-region: drag' set, positioned right up against the edge of its owning resizable BrowserWindow, prevents the owning BrowserWindow from being resized from that edge.
Testcase Gist URL
https://gist.github.com/9cb18987a6a87f7b44581511d7def0e1
Additional Information
I believe there is an approximately 6px wide event edge that exists on the edges of BrowserWindows which is reserved for drag handles (resizing the window) - it takes precedence over the DOM in that region, at least in the webContents of a BrowserWindow. However it appears when a BrowserView is butted right up against the edge of its containing BrowserWindow with -webkit-app-region: drag set, the drag region is taking precedence over the resize region, preventing window resize from that edge.
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!
Confirmed this issue still exists on latest stable 21.1.0.
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue.