browserView.setBounds causes issues with focus and clicks if position is not x=0, y=0

[mchataigner]

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 an issue that matches the one I want to file, without success.

Issue Details

• Electron Version:
  • 9.x, 10.x, 11.x
• Operating System:
  • macOS 11.0.1 (was on macOS 10.15.7 with same issue before BigSur upgrade) (no issue on GNU/Linux, and not tested on Windows)
• Last Known Working Electron version:
  • N/A

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

$ git clone https://github.com/mchataigner/electronsample.git -b main
$ npm install
$ npm start

Screenshots

Additional Information

[praneetrohida]

Did not have this issue on v10.1.5. It started happening after I upgraded to v11.0.3.

[sirtimid]

@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?

[andycreeth]

We are also experiencing this issue with stream-labs/streamlabs-obs. We use a BrowserView positioned on the right side of the window. On version 9.3.4, the entire BrowserView is being treated as a drag region, and is not interactable. We are downgrading to 9.3.3 on macOS for now, which resolves the issue.

The top post in this issue seems pretty complete, but happy to provide any additional details.

[sirtimid]

@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?

[codebytere]

hey @sirtimid 9.x.x is mostly security now but i can try :)

[sirtimid]

hey @sirtimid 9.x.x is mostly security now but i can try :)

thank you!! :)

[praneetrohida]

Is there any update on this issue? This has been blocking us from upgrading to 11

[codebytere]

@praneetrohida oops thanks for the ping! i already fixed this actually, in #27147 - latest 11 should contain it :)

[sirtimid]

@codebytere but it wasn't backported on 9.x.x :(