search

aurelia-ui-toolkits / aurelia-kendoui-bridge

MIT License
117 stars 31 forks source link

esnext-aspnetcore tutorial sample browser dependency issue #681

Open adriatic opened 7 years ago

adriatic commented 7 years ago

The sample at https://github.com/adriatic/kendo-tutorials/tree/master/esnext-aspnetcore behavies weird - if works just fine in Firefox, while failing silently in chrome.

The details of creating this sample are here: https://github.com/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/675#issuecomment-271417874

adriatic commented 7 years ago

I rebooted my machine and this problem cannot be reproduced any more. Leaving this issue open as a reminder to check this again in a few days

adriatic commented 7 years ago

Today, I added the typescript aspnetcore navigation skeleton and observed the identical behavior as above - the finished sample runs fine in Firefox, where in Chrome it acts as if the autocomplete components was not added.

It looks like a caching issue - but I have a feel that it is more likely something Chrome specific.I would appreciate making a clone of this sample and running it as described in https://github.com/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/675#issuecomment-271678991 section of my "raw" set of tutorial documents.

Even after rebooting my machine, Chrome shows this:

image

Using the Chrome developer tools it is easy to see that the code for autocomplete and the changes in app.js (added route) cannot be viewed.

At the same time Firefox renders this

image

(both taken one after another, with the app running in the console window)