NW.js v0.13.0-beta6 released

Roger Wang

unread,

Feb 17, 2016, 4:26:48 AM2/17/16

to nw.js

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

We are pleased to announce NW.js 0.13.0-beta6. Chromium 48 is updated to 48.0.2564.109 from 48.0.2564.97. Node.js is updated to v5.6.0. Multiple bugs were fixed and a few features left in 0.12 were ported.

NW.js is able to support native modules built by node-gyp/npm now. 'nw-gyp' is not needed any more. See more information here:https://groups.google.com/d/msg/nwjs-general/UqEq8ito2gI/W-ld9LSoDQAJ

We'll look into upgrading to Chromium 49 before RC release.

Chromium 48 brings exciting changes including custom buttons in the notification; VP9 as the codec for WebRTC, seehttp://blog.chromium.org/2015/12/chrome-48-beta-present-to-cast-devices_91.html . You can use them in your NW app today.

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

An important internal change in this release is that the Window object returned by nw.Window.get() resides in the background page. It's a 'shadow' object and its prototype points to the actual (inner) Window object in DOM context, which we returned by the function in previous releases. This change is for supporting navigation in the target window. After navigation, the previously returned Window object is still functional and its prototype is updated with the new inner Window object. This change doesn't affect our API.

ChangeLog

Update Chromium to 48.0.2564.109
Update Node.js to 5.6.0
support controlling window with external page
Fix: enable self extraction (#4071)
Fix: crash when using native modules in OSX (#4338)
Fix: FileReader not working (#4399)
Fix: console tab with DevTools jail not working until switch frame manually
Fix: OSX menu support broken (#4374)
Fix: JavaScript dialogs text (#4190)
Fix: Typo: rename App.(un)registerGlobalHotkey to App.(un)registerGlobalHotKey
Fix: Window.zoomLevel changes all windows (#4352)
Fix: avoid polluting global namespace with 'path' etc. (#4350)
add URL scheme support for MAC (#4240)
support 'new_instance' option for Window.open
support native modules built by node-gyp
[docs] update for new_instance etc

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

Download

SDK build:

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

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

Roger Wang

unread,

Feb 17, 2016, 9:20:20 AM2/17/16

to nw.js

Actually the issue - add URL scheme support for MAC (#4240) is not fixed in this version. Will fix it soon.

Roger

nw.e...@gmail.com

unread,

Feb 17, 2016, 8:28:57 PM2/17/16

to nw.js

Regression from NW.js 0.13.0-alpha6:

I notice that the "Printing" Chrome-* API sample app from the chrome-app-samples-master repo,

which was working (Print Preview window) up through alpha6, is not able to open the Print Preview in

the Beta releases due to some JS errors:

Has the "pdf.dll" included in the NWjs builds replace this chrome-API ? Is it functional as yet?

Thank you for your consideration to this issue>

Jonathan Dodd

notsospecial1

Roger

unread,

Feb 17, 2016, 8:31:26 PM2/17/16

to nw.e...@gmail.com, nw.js

Thanks for reporting. Will look into this.

PDF support should be fully functional as in Chromium browser. In recent versions of Chromium, pdf.dll was replaced by an internal extension.

Roger

--
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 Wang

unread,

Feb 17, 2016, 10:03:00 PM2/17/16

to nw.js, nw.e...@gmail.com

It now looks like an issue in either the sample or Chromium 47 (and later), to which we updated in alpha7.

In document.js:39 in the sample: this.domWindow.frames['print'], it evaluates to the 'print()' function of a DOM window, not the DOM window in the iframe named 'print'.

The upstream issue is here: https://code.google.com/p/chromium/issues/detail?id=438923

Could you verify the sample working in Chromium 48?

Roger

nw.e...@gmail.com

unread,

Feb 18, 2016, 12:09:06 AM2/18/16

to nw.js

Roger:

"Printing" Chrome-* sample WORKS (with Print preview) through NW.js 0.13.0-Alpha6 -- so it seems related to Chromium 47+ boundary.

It has the JS errors (so, NO Print preview) in Alpha7, Alpha8, and all Betas so far.

(Sorry for delay in reply... I had to re-deploy several of the older alpha- SDK builds.)

Thanks again,

Jonathan Dodd

notsospecial1

Roger

unread,

Feb 18, 2016, 12:33:55 AM2/18/16

to nw.e...@gmail.com, nw.js

I mean I t hink the error should be present in upstream Chromium browser too.

--

11981...@qq.com

unread,

Feb 23, 2016, 10:26:23 PM2/23/16

to nw.js

强烈建议成立中文社区,以及中文网,这技术在中国区也很流行!
It is strongly recommended that established Chinese community and Chinese, this technology is very popular in China also!

在 2016年2月17日星期三 UTC+8下午5:26:48，Roger Wang写道：

Reply all

Reply to author

Forward