You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When two views request the same resource while loading the app, then the second view seems to assume that the resource has finished loading, and tries to add it (null) to DOM, and sets _alreadyGloballyInjected to true. Resulting in nothing added. (when the first request finishes loading, it first checks _alreadyGloballyInjected, which is true, so it just bails)
finder.html:
<require from="./finder.css"></resource>
finder-results.html
<require from="./finder.css"></resource>
Expected/desired behavior:
I haven't been able to reproduce it yet in a less complex app, probably because the resources load instantly..
What is the expected behavior?
The second view should wait for the resource to finish loading before trying to process it. Or it shouldn't try to process it at all, because the first view already is doing that.
My workaround:
css-resource.js:
function beforeCompile(content, resources, instruction) {
if (this.css === null) return;
The text was updated successfully, but these errors were encountered:
I'm submitting a bug report
1.0.rc
Please tell us about your environment:
Windows 10
6.3.0
3.10.3
webpack 2.1.0-beta.17
all
TypeScript 2.0
Current behavior:
When two views request the same resource while loading the app, then the second view seems to assume that the resource has finished loading, and tries to add it (null) to DOM, and sets
_alreadyGloballyInjected
totrue
. Resulting in nothing added. (when the first request finishes loading, it first checks_alreadyGloballyInjected
, which is true, so it just bails)finder.html:
finder-results.html
Expected/desired behavior:
I haven't been able to reproduce it yet in a less complex app, probably because the resources load instantly..
The second view should wait for the resource to finish loading before trying to process it. Or it shouldn't try to process it at all, because the first view already is doing that.
My workaround:
css-resource.js:
The text was updated successfully, but these errors were encountered: