You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nwjs-upgrade branch (PR #275) has finally been merged into master, which gives us the latest NW.js (0.18.7) including the latest NodeJS and Chromium and many bugfixes on all platforms.
Unfortunately, the old notification system of NW.js had been removed with the release of 0.13.0 and the only way of displaying notifications was using Chromium's rich notifications which are not integrated into the OS/DE. This meant that a rewrite of the notification system was necessary to be able to avoid these kind of regressions.
Luckily, starting with Chromium 52.x (NW.js 0.16.0), native notifications are now available under a feature flag in Chromium on MacOS and can be used without relying on 3rd party software. But unfortunately again, there is no control of the notification actions (settings button) and the default Chromium behavior is being used, which will open a new blank window when clicking the button. This is a bug in NW.js.
The text was updated successfully, but these errors were encountered:
This has been fixed in NW.js 0.25. The notification system has been rewritten and merged into the master branch with NW.js 0.26.1 and native notifications for macOS and Linux provided by Chromium.
The
nwjs-upgrade
branch (PR #275) has finally been merged into master, which gives us the latest NW.js (0.18.7
) including the latest NodeJS and Chromium and many bugfixes on all platforms.Unfortunately, the old notification system of NW.js had been removed with the release of
0.13.0
and the only way of displaying notifications was using Chromium's rich notifications which are not integrated into the OS/DE. This meant that a rewrite of the notification system was necessary to be able to avoid these kind of regressions.Luckily, starting with Chromium
52.x
(NW.js0.16.0
), native notifications are now available under a feature flag in Chromium on MacOS and can be used without relying on 3rd party software. But unfortunately again, there is no control of the notification actions (settings button) and the default Chromium behavior is being used, which will open a new blank window when clicking the button. This is a bug in NW.js.The text was updated successfully, but these errors were encountered: