Closed mmorrisontx closed 8 years ago
Update, it seems to actually happen in all windows, not just non-resizable ones. Not sure how I missed that. Updated first post.
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.
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.
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.