atom electron issue ~13

[pYr0x]

i see that done-autorender uses can-zone.
i created a test with and without done-autorender
https://github.com/pYr0x/testapp

• if i create an app for electron without done-autorender, all works
• if i test the app with done-autorender in the browser (chrome), all works.
• if i create an app for electron with done-autorender, it fails.

are there known issues with can-zone and electron?
electron use Chrome 49

[matthewp]

Sorry I missed this, will try to get to it this week.

[frank-dspeed]

@pYr0x are you using websockets?

[pYr0x]

no

[frank-dspeed]

@pYr0x donejs/autorender#68 test if that fixes also your issue in electron i think it will

[matthewp]

I tried getting your project updated but apparently there's some stuff in there that's too old :( .
Anyways, if you can get it working again I'd love to take a look at what is going on here. pYr0x/testapp#1

[frank-dspeed]

@matthewp you can close this as with current methods it works diffrent in future done-autorender will get totally ignored for my current canes release this is the case as i use .js entry point that returns a Component and i don't use a .stache entry point for loading i am working on ssr nativ for canes/canjs

[frank-dspeed]

@matthewp zones are working correctly inside elctron in general is also a reason to close this