NW.js v0.13.0-beta3 released

330 views
Skip to first unread message

Roger Wang

unread,
Jan 12, 2016, 10:12:07 PM1/12/16
to nw.js

http://nwjs.io/blog/v0.13.0-beta3/


We are pleased to announce NW.js 0.13.0-beta3. After the beta announcement, thanks to the bug reports from many users, we have been fixing the issues and release a new version now. We'll keep watching issue reports and release new versions regularly. Hopefully we can reach RC state after a month. beta3 is a bug fix release with no new features or upstream updates. In the next beta version Chromium will be updated to 48 and Node.js will be updated too.


If you're new to this major new beta version 0.13, please read http://nwjs.io/blog/v0.13.0-beta1/


ChangeLog

  • Fix: save as... dialog not working (#4142)
  • Fix: app with hidden window will quit on start on osx
  • Fix: chrome socket api permission in NW app (#4143)
  • Fix: some Node core modules not working after close window (#4130, #4140)
  • Fix: chrome.fileSystem.restoreEntry breaks retainID on app reload (#4150)
  • Fix: oauth not working due to browser side naviagation (#4179, #4131, #4184)
  • Fix: Exception in nw.dll when running native module serialport (#4152)
  • Fix: window.open not loaded using node-remote (#4180)
  • Fix: POST form not working on navigation
  • Fix: nwjs Helper process not closed (#4118)
  • Fix: NW.js doesn't quit if DevTools has opened once (#4164)
  • Fix: window not closed when listen to 'close' event in another window (#4138)
  • Fix: [WIN] debug build of 'payload' tool
  • Fix: Crash when using devtools to view some source (#4121)
  • Fix: nw.Window.get() returns null after navigation (#4157, #4007)
  • Fix: requrie() function in the shim for nw12 compatibility (#4141)
  • Fix: Reversed x and y in win.moveTo and win.moveBy (#4136)
  • Accept array of matched patterns in node-remote (#4132)
  • [doc] Added docs for win.navigation event
  • [doc] Updated docs for single-instance
  • [doc] add hint for document contribution
  • [doc] update for Multiple Context mode
  • [doc] For Users > Getting Started. Revise example 2 sample code to cater new NW.JS API for Menu
  • [doc] update for Window.id

Download

SDK build:

NaCl build and other platforms: http://dl.nwjs.io/v0.13.0-beta3/


There are 3 builds for each platform - normal build, sdk build and Nacl build. Normal build doesn't have devtools, only SDK build does. lt can be opened by pressing F12 (Cmd-Alt-I on OSX). SDK packages also have more development tools to be exposed in the following releases, as well as the NaCl support.


Our build infrastructure enables live binary build from git tip so you can access to the latest binary from http://dl.nwjs.io/live-build/


Known issues

http://docs.nwjs.io/en/latest/For%20Users/Migration/From%200.12%20to%200.13/#known-issues

lithi...@gmail.com

unread,
Jan 13, 2016, 2:48:58 PM1/13/16
to nw.js
Keep up the good work, thank you.

eivi...@gmail.com

unread,
Jan 15, 2016, 4:31:55 AM1/15/16
to nw.js
I'm on 64-bit Linux Mint 17 KDE and all three of the v.0.13.0 betas just hang waiting for KDE Wallet (which I have disabled), so I'm not able to launch anything. No window is spawned, and there's no KWallet popup for me to dismiss. I have reported the issue under the Chromium repository, and hope that's the right place.

Ashley Gullen

unread,
Jan 15, 2016, 7:24:01 AM1/15/16
to Roger Wang, nw.js
A lot of Construct 2 users are reporting ghost processes left behind after closing, including in beta3: https://www.scirra.com/forum/nwjs-not-completely-closing-when-exiting-app_t166669

I've not actually been able to reproduce this at all, but is it a known issue?

Ashley


--
You received this message because you are subscribed to the Google Groups "nw.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-general...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Roger

unread,
Jan 18, 2016, 1:18:45 AM1/18/16
to Ashley Gullen, nw.js
We've fixed issues like this and add them to tests. There is no known issue like this now. And it should be easy to reproduce. 

I think it may make a difference when they clear the user data directory and try again. That could be the difference between systems.

Roger
Reply all
Reply to author
Forward
0 new messages