I'm noticing an increase in window width when the application is restored from the taskbar (Windows 7, 64-bit) after it has been minimized.
This happens even when resizable is set to false, or when all the height and width options (default, min, max) are set to the same value in package.json - in my case 1024w X 768h.
See the attached image for an example.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
I'm hitting this bug as well.
Using node-webkit 0.5.1, Win7 x64
@CommissarXiii As a workaround, are you able to use DOM events (window.resize) to undo and revert the window size change?
I might give this a shot later to see if I can whip up a client-side workaround for this, but we really do need a proper fix in node-webkit itself.
Has this been looked into further? This is a major annoyance within a windows environment.
I can work around this by catching the minimize event, save the window width, catch the restore event and then setting the window width back to the saved width, but when you hide the window with [Windows key]+d, a user of my app just reported to me that this workaround doesn't work, so I'd guess the minimize event doesn't get triggered in that case.
to fix nwjs/nw.js#253 issue and to support future themes with arbitra…
This is still an issue in the 0.8 branch. It does not appear to affect frameless windows. Is there some type of compensation being made for the window frame on Windows that would cause this (beyond the initial addition of width so the viewport matches package.json)?
Console Output showing the issue. window.frame == require("nw.gui").Window.get()
716 (set to 700 in package.json)
638 (set to 600 in package.json)
Workaround from the above commit seems to resolve the issue (removing min_width and min_height from package.json), but it is a poor substitute.
+studiochris removed the min_width and min_height
then worked fine...
we need set min_width and min_height in app ..
or set "frame": false,