[LTS] nwjs 0.16 - MacOS 10.10 - nw.global.__nw_windows not correct
See original GitHub issueMy app handles the running instances of every window and it was working good with 0.14 & 0.15.
On v 0.16 I see there is some problem with nw.global.__nw_windows
It doesn’t store always the right number of opened windows.
E.g. if I open 5 windows I see just 2 NWWindow object inside nw.global.__nw_windows
Issue Analytics
- State:
- Created 7 years ago
- Comments:22 (8 by maintainers)
Top Results From Across the Web
NW.js v0.14.7 (LTS) Released
In LTS branch, NW.js 0.14.7 is released with all the new features and ... is not set correctly; Fix: crash on JSON.stringify(window) (#4959) ......
Read more >Changelog - Cypress Documentation
Fixed an issue with Angular Component Testing where urls within SASS/SCSS files were not being correctly resolved which could result in incomplete styling....
Read more >Vulnerability Summary for the Week of February 10, 2020 | CISA
Primary Vendor ‑‑ Product Published CVSS Score
adobe ‑‑ framemaker 2020‑02‑13 10
ajaxeplorer ‑‑ ajaxeplorer 2020‑02‑11 10
artica ‑‑ pandora_fms 2020‑02‑12 9
Read more >Node - CVE - Search Results
This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a...
Read more >Full text of "The Performance Of Open Source Applications
Global resource and network optimizations: the browser is able to make ... many different platforms: Linux, Windows, OS X, Chrome OS, Android, and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Google just released another Chromium stable update in the next day after the previous one. So I’m going to release 0.17.3 soon and this issue will be likely slip into 0.17.4.
Will see this before 0.17.3. I was about to fix it in 0.17.2 but was occupied by upstream release with security updates.
On Wed, Sep 14, 2016, 9:43 PM AndryBray notifications@github.com wrote: