Mouse Dead Zone #321

Closed
sonicsnes opened this Issue Jan 7, 2013 · 4 comments

Comments

Projects
None yet
6 participants
Contributor

sonicsnes commented Jan 7, 2013

For all windows, there exists a zone near the entire outer border of the window which eats mouse clicks.

This can be replicated easily by running the "menus" demo, and attempting to right click near the edge of the window. No menu will appear.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor

sonicsnes commented Jan 8, 2013

Update, it seems to actually happen in all windows, not just non-resizable ones. Not sure how I missed that. Updated first post.

sonicsnes added a commit to sonicsnes/node-webkit that referenced this issue Jan 24, 2013

Remove window draw radius and fix framed mouse capture area on windows
1px draw radius is unnecessary for nw and causes a 1px artifact at the corner of all windows
Fixes nwjs/nw.js#331

We create a mouse dead zone on frameless windows, because the drag handles are only available within the window border -- not outside (as the case is for framed windows). The if block was incorrectly only covering the dead zone on one side of the window -- not all four.
Fixes nwjs/nw.js#321

@rogerwang rogerwang closed this Jan 25, 2013

Unfortunately it seems like this issue is back with 0.10.5 on windows. (only tested windows 7)
I've tested with the basic Frameless window demo and resizable:false in manifest.json.
The 5 outer most pixels on all edges of the window are dead.

@rogerwang rogerwang reopened this Sep 17, 2014

@rogerwang rogerwang self-assigned this Sep 17, 2014

@tommoor tommoor added the bug label Dec 16, 2014

Ran into something similar. You can click in that area, however, hover states don't register within that area.

This should be working with latest version now.

In 0.13 we changed to an optimized architecture so more features can be supported, see http://nwjs.io/blog/whats-new-in-0.13/ and it's good for keeping up with Chromium upstream -- we released with Node.js v6.0 and new Chromium versions within 1 day after upstream release.

The new version would fixed many issues reported here and we're scrubbing them. This issue is closed as we believe it should be fixed. Please leave a message if it isn't and we'll reopen it.

@nwjs-bot nwjs-bot closed this Jun 14, 2016

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