NW.js Plugin Broken In Preview (v0.27.0)

Problem Description

The most recent stable release of NW.js (v0.27.0) gives a JS error message on startup caused by the NWjs plugin.

Attach a Capx

Blank project with the added NW.js plugin.

Steps to Reproduce Bug

• Create new blank project
• Add the NW.js Plugin
• Preview using NW.js v0.27.0

Observed Result

Construct 2 displays the following error message when starting preview:

Javascript error! Uncaught TypeError: Cannot set property 'onchange' of nullhttp://192.168.2.120:50000/NodeWebkit_plugin.js, line 90 (col 35)[/code:g5as70d4]
Console says the following:
[code:g5as70d4]Uncaught TypeError: Cannot set property 'onchange' of null
    at pluginProto.Instance.instanceProto.onCreate (NodeWebkit_plugin.js:90)
    at Runtime.loadProject (preview.js:1482)
    at XMLHttpRequest.xhr.onload (preview.js:414)[/code:g5as70d4]

[b]Expected Result[/b]
It should preview games just like it did in the previous versions.
    
[b]Affected Browsers[/b]
[ul]
    [li] NW.js (YES)
    [/li][li] Chrome: (NO)
    [/li][li] FireFox: (NO)
    [/li][li] Internet Explorer: (NO)[/li][/ul]
    
[b]Operating System and Service Pack[/b]
Win7 SP1, up to date drivers.
    
[b]Construct 2 Version ID[/b]
r249 (beta)

It looks like a bug in the NW.js 0.27 update. I don't think we can work around this, but hopefully it's straightforward and the next NW.js update can fix this. Filed an issue here: https://github.com/nwjs/nw.js/issues/6321

Thanks for the report, I hope this will be backported to all older versions as well.

As far as I'm aware, only NW.js 0.27 is affected, and the issue is in NW.js itself so we don't need to change C2 when it's fixed, just issue a new NW.js update.

Does this mean that nwjs 0.27 will be dropped from the list? By backporting I basically meant backported into that specific version.

(Nevermind you've already asked the question, will subscribe and wait for their response.)

Uninstalled 0.27.0 and used v0.26.0 and all is good.

Just released NW.js 0.27.2 which should fix this. Can you confirm?

Just released NW.js 0.27.2 which should fix this. Can you confirm?

Yep everything is alright now, preview works as intended. This bugreport can be closed.

If this didn't get backported into v0.27.0, I'd recommend removing it from the downloads page.

Would make things easier for people that don't know about this issue. Thanks for doing all the reporting work!