You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!DOCTYPE html><htmlstyle="background:rgba(0,0,0,0.5);height:100%"><head></head><body><divstyle="background:red;position:absolute;right:0;top:0;">TEXT</div><buttononclick="resize();return false;">Click to maximize/restore</button><script>varis_maximized=false;vargui=require("nw.gui");varwin=gui.Window.get();win.on("restore",()=>is_maximized=false);win.on("maximize",()=>is_maximized=true);functionresize(){if(is_maximized){win.restore();}else{win.maximize();}}</script></body></html>
Expected behavior:
Screenshot showing the expected behavior of the top right corner when the app is maximized
Current behavior:
Screenshot showing the problem at the same location
Screenshot showing the problem at the bottom right position when changing the TEXT style from top: 0 to bottom: 0
The entire top, right and bottom areas go beyond the expected limits.
This might be a consequence of the fix for #6221, #6219 or #6204
The text was updated successfully, but these errors were encountered:
NWJS Version : SDK 0.27.0-beta1 and SDK 0.26.2
Operating System : Win7 x64 and Win10 x64
Expected behavior
The top, right and bottom limits should be respected when maximizing the window
Actual behavior
The window content goes beyond the expected limits when maximized
How to reproduce
Sample app with window set to transparent frameless.
Using
package.nw
method, sample can be found belowpackage.json
index.html
Expected behavior:
Screenshot showing the expected behavior of the top right corner when the app is maximized
Current behavior:
Screenshot showing the problem at the same location
Screenshot showing the problem at the bottom right position when changing the
TEXT
style fromtop: 0
tobottom: 0
The entire top, right and bottom areas go beyond the expected limits.
This might be a consequence of the fix for #6221, #6219 or #6204
The text was updated successfully, but these errors were encountered: