NW.js v0.26.0 Released with Chromium 62, Node 8.7.0 and Security Updates

48 views
Skip to first unread message

Roger Wang

unread,
Oct 18, 2017, 3:00:27 AM10/18/17
to nwjs-g...@googlegroups.com

We're excited to announce NW.js 0.26.0 with Chromium 62 upgrade, security updates within it and Node 8.7.0.

Chromium 62 contains usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore. It supports Network Quality Estimator API, OpenType variable fonts, and media capture from DOM elements. Please check upstream information here. The stable upgrade contains many security fixes as well.

We made the 0.26 branch ready soon after Chromium beta bumps to 62. Thanks to the testers for their valuable feedback and bug reports. We've been working on 3 branches simultaneously: a released branch on current Chromium stable, a beta branch on Chromium beta and a 0.14 branch for legacy OS support.

ChangeLog

  • Update Chromium to 62.0.3202.62
  • Update Node.js to v8.7.0
  • Support scale option for printing (#6166)
  • Fix: Maximizing an always on top transparent frameless window causes the bottom to overflow under the taskbar (#6204)

Full ChangeLog: https://github.com/nwjs/nw.js/blob/nw26/CHANGELOG.md

Download

SDK build:

Binary for other platforms: https://dl.nwjs.io/v0.26.0/

There are 2 builds for each platform - normal build, and SDK 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 https://dl.nwjs.io/live-build/

Known issues

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

f...@bebo.com

unread,
Oct 24, 2017, 1:35:36 PM10/24/17
to nw.js
Hi Roger,

for those of us who build NW.js for windows, it seem that upstream has switched to Visual Studio 2017 update 3.2 with the 15063 (Creators Update) Windows SDK since September, 2017 (R503915).

I assume starting with NW.js 0.26.0 we should as well?

Thx,
Florian

Roger

unread,
Oct 24, 2017, 6:21:05 PM10/24/17
to Florian Nierhaus, nw.js
No. It's effective starting from Chrome 63 in upstream thus NW 0.27.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages