Closed txels closed 9 years ago
Investigating a bit further, the leak only happens between applications served by the same backend process (I run the apps locally using gulp watch
), so it may have to do with how that development server handles live reload.
This is not a bug (or feature) of aurelia. This is because of the browsersync plugin (https://github.com/aurelia/skeleton-navigation/blob/master/build/tasks/serve.js#L8-L18). You can disable this by setting the ghostmode property of browsersync to false (http://www.browsersync.io/docs/options/#option-ghostMode).
Oh gosh thanks, it was driving me crazy. It could be added to the tutorial documentation (or be a default setting in the skeleton app).
Same here, I was not knowing this On 28-Sep-2015 1:20 PM, "Carles Barrobés i Meix" notifications@github.com wrote:
Oh gosh thanks, it was driving me crazy. It could be added to the tutorial documentation (or be a default setting in the skeleton app).
— Reply to this email directly or view it on GitHub https://github.com/aurelia/framework/issues/218#issuecomment-143662984.
How bout this? https://github.com/aurelia/skeleton-navigation/pull/176
Nice, thanks for the speedy responses.
I have this weird problem with Aurelia apps. If I have the same app open in multiple browsers (either browser tabs or even different manufacturers' browsers), then what I type on forms in one browser leaks to the other one. This is one example with Chrome and Firefox:
It doesn't even have to be the same page from the app and the same form. It happens across different pages.
There is nothing particular with my app and forms rather than using the regular Aurelia two-way data binding. In fact, I can reproduce this problem with the aurelia skeleton app.
The leak doesn't happen across different applications (i.e. my app and the skeleton app do not leak to each other).