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

Frameless windows break mouse cursor on High DPI monitors with scaling #14787

sbatten opened this Issue Sep 24, 2018 · 2 comments


3 participants
Copy link

sbatten commented Sep 24, 2018

  • Operating System (Platform and Version): Ubuntu 18.04 amd64

Tested Electron version 2.0.9 and 3.0.0

Expected Behavior
Elements set with cursor text should show the text cursor when using frameless windows on High DPI monitors with scaling higher than 100%.

Actual behavior
When using higher than 100% scaling on a high dpi monitor and frameless electron windows, elements with a text cursor revert to the default cursor half-way down the element.

To Reproduce
In VSCode you can enable the custom title bar by setting window.titleBarStyle to custom. This will use a frameless window. On a high DPI monitor with your display settings set to 200%, you can see that mousing around the editor reveals this bug. You can also repro this using Electron Fiddle and a single div in the page with cursor set to text. Make sure the div is fairly large (say 500px).

Initially reported in VSCode: Microsoft/vscode#58383 (comment)


This comment has been minimized.

Copy link

welcome bot commented Sep 24, 2018

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

To help make it easier for us to investigate your issue, please follow the contributing guidelines.


This comment has been minimized.

Copy link

joaomoreno commented Dec 3, 2018

Filed before: #13911

There's a fiddle in there which you can just load up in Electron Fiddle:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment