-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Windows snap is lost with frameless transparent window and webkit-app-region drag #6219
Comments
I can reproduce this issue on Windows with nwjs-sdk-0.26.0. |
CC @jtg-gg , please take a look. Thanks in advance. |
Looks like this is an issue with smaller window size. We are developing a snapping application and facing same issue on windows platform. Window size is pretty much same as shown in problem here. Even elctron is facing similar issue and they have left it to Chromium and closed this issue as won't fix (electron/electron#2170) |
@kapilmoondra Nevermind the above, I thought this was #6221 |
@rogerwang I've made a pull request nwjs/chromium.src#98 |
This is fixed in git and will be available in the next nightly build. |
NWJS Version : SDK 0.26.0
Operating System : Win7 x64
Expected behavior
Window snap should stay working as normal with frameless transparent window
Actual behavior
Window snap is completely lost
How to reproduce
Window snap behavior can be previewed here for better understanding: http://i1-news.softpedia-static.com/images/news2/snap-in-windows-10-overview-and-enhancements-489110-4.gif
Using a basic app, move the window against top or side edges of the screen, it should display the snap preview and letting it go will cause it to resize the app on its own to the preview size.
Instead there is no recognition of window snap and the described behavior is absent, the window never resizes
App sample using
package.nw
folder:I don't know if this is expected behavior, meaning that this is meant to be like this when using a transparent frameless window, but thought it should be reported in case it is a bug.
The text was updated successfully, but these errors were encountered: