NW.js v0.14.0 Released with Chromium stable 50

Roger Wang

unread,

Apr 14, 2016, 12:16:31 AM4/14/16

to nwjs-g...@googlegroups.com

We are excited to release NW.js 0.14.0 with latest Chromium stable 50.0.2661.75.

See upstream blog for exciting new features and improvements in Chromium 50: http://blog.chromium.org/2016/03/chrome-50-beta-push-notification.html

Following our release plan in 2016, we want to release a new major version as soon as a new Chromium stable release. After 3 RC versions in the beta branch for 0.14 with Chromium 50, we make the final version available within 24 hours following upstream relase. Thanks to all the users reporting issues and feedback.

We've been working on 2 branches simultaneously: a released branch on current Chromium stable; and a beta branch on Chromium beta. In the past 0.13.x and 0.14.0-rc releases, as soon as an version is available in upstream, we released the updated NW.js within 24 hours. This is helpful to deliver new features and security fixes to users in time.

For more information on the new milestone 0.13 and later versions which has an optimized architecture, please see our blog "What's New in 0.13" for a better introduction.

ChangeLog

Update Chromium to 50.0.2661.75
Fix: AlwaysOnTop does not work with Fullscreen or overlapping toolbar (#4554)
Fix: Window object from nw.Window.open is null after an new_instance window was opened (#4691)
Fix: Linux Fedora application menu says 'nwjs' instead of package.json name (#4693)
Fix: Shortcut not work in devtools while it placed in a webview (#4709)
Fix: nw.App.clearCache hang and it should be sync (#4674)
Fix: Crashes sometimes when using menu.popup and GC happens (#4697)
Fix: Win.isFullscreen and isAlwaysOnTop should not be function (#4446)

Full changelog: https://github.com/nwjs/nw.js/blob/nw14/CHANGELOG.md

Download

SDK build:

NaCl build and other platforms: http://dl.nwjs.io/v0.14.0/

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

wombat...@gmail.com

unread,

Apr 14, 2016, 12:53:22 PM4/14/16

to nw.js, ro...@nwjs.io

Good work Roger, keep up the great work!

Frank Hale

unread,

Apr 15, 2016, 10:33:57 AM4/15/16

to nw.js, ro...@nwjs.io

I have a question based on the following text from the release notes:

"Following our release plan in 2016, we want to release a new major version as soon as a new Chromium stable release. After 3 RC versions in the beta branch for 0.14 with Chromium 50, we make the final version available within 24 hours following upstream relase. Thanks to all the users reporting issues and feedback."

Does the new release plan for 2016 also take into consideration Node releases? Node is currently on 5.10.1 but NW.js is still on 5.10.0. It would be very nice if the release plan would also consider these new releases.

Thank you to everyone involved for your awesome work on NW.js!

baldwi...@gmail.com

unread,

Apr 16, 2016, 5:43:04 AM4/16/16

to nw.js, ro...@nwjs.io

Quick warning for people using webgl in nw; there is a regression in Chromium 50 which breaks detection of WEBGL_draw_buffers extension support. Trying to use 0.14 at this point will return:

ERROR: 0:1: 'GL_EXT_draw_buffers' : extension is not supported

If your nw app uses that extension you'll have to stick with nw 0.13 until https://bugs.chromium.org/p/chromium/issues/detail?id=586536 lands in chromium and gets pulled into nw.

Took me a while to track down the problem so hopefully by posting here I'll save someone some time!

Roger Wang

unread,

Apr 17, 2016, 8:26:06 AM4/17/16

to nw.js

Yes. We would like to follow Node.js releases closely as well.

Thanks,

Roger

Reply all

Reply to author

Forward