-
Notifications
You must be signed in to change notification settings - Fork 16k
browserView.setBounds causes issues with focus and clicks if position is not x=0, y=0 #26681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Did not have this issue on v10.1.5. It started happening after I upgraded to v11.0.3. |
@codebytere This issue was caused by this PR #26322 It has to do with draggable regions, they are not calculated properly. There is a region at the end of the BrowserView that is the height of the top offset and it is draggable. Probably you should use BrowserWindow.height not BrowserView.height to exclude the draggable region? |
We are also experiencing this issue with stream-labs/streamlabs-obs. We use a The top post in this issue seems pretty complete, but happy to provide any additional details. |
@codebytere So I see this was fixed for mac on #26690 and for windows on #26738 Can you backport the fixes on 9.x.x please? |
hey @sirtimid 9.x.x is mostly security now but i can try :) |
thank you!! :) |
Is there any update on this issue? This has been blocking us from upgrading to 11 |
@praneetrohida oops thanks for the ping! i already fixed this actually, in #27147 - latest 11 should contain it :) |
@codebytere but it wasn't backported on 9.x.x :( |
Preflight Checklist
Issue Details
Expected Behavior
When a BrowserView is set to a position other than x=0, y=0, the whole viewable view should be focusable/clickable.
Actual Behavior
When I set a BrowserView with bounds { x=0, y=150, width=window.width, heigth=window.height-150}, there is a rectangle at the bottom of the window of 150 pixels high where I cannot click.
To Reproduce
I’ve create a small project to reproduce https://github.com/mchataigner/electronsample
Screenshots
Additional Information
The text was updated successfully, but these errors were encountered: