NW.js v0.24.4 Released

54 views
Skip to first unread message

Roger Wang

unread,
Aug 25, 2017, 3:46:02 AM8/25/17
to nwjs-g...@googlegroups.com

This release is for Chromium 60 minor update and bug fixes. It should be the last 0.24 release as 0.25.0 will be released soon. In this version, renaming the macOS helper application is supported by using a new field in manifest.

Chromium 60 features Paint Timing API, CSS font-display, and Credential Management API improvements. See the upstream announcement for more information. You can read the guide here also. The stable upgrade contains many security fixes as well.

We made the 0.24 branch ready soon after Chromium beta bumps to 60. 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.

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

ChangeLog

  • Update Chromium to 60.0.3112.113
  • Support rebranding the Helper app on macOS (#6103)
  • Partly support loading Node inspector module in forked process (#6115)
  • Fix: crash on macOS : chrome.windows.create() (#6113)
  • Fix: crash on start in macOS 10.9 (#6108)
  • [docs] support renaming the helper application under macOS.

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

Download

SDK build:

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

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

Reply all
Reply to author
Forward
0 new messages