Remove async workaround for Chromium bug #55
Comments
tomalec
added a commit
that referenced
this issue
Aug 22, 2018
tomalec
added a commit
that referenced
this issue
Aug 22, 2018
tomalec
added a commit
that referenced
this issue
Aug 22, 2018
http://crbug.com/389566 Remove asynchronous import of partials. #55
tomalec
added a commit
that referenced
this issue
Aug 28, 2018
Add test-case and remove workaround for fixed chromium bug,
tomalec
added a commit
to Starcounter/StarcounterClientFiles
that referenced
this issue
Aug 29, 2018
Removes chromium bug workaround Juicy/imported-template#55, makes the flow more synchronous, reduces the reasons of FOUC
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have quite an old workaround for Polymer/polymer#554, http://crbug.com/389566
https://github.com/Juicy/imported-template/blob/master/imported-template.html#L91-L99
Even though https://bugs.chromium.org/p/chromium/issues/detail?id=521692&desc=2 is still opened, use case closer to us webcomponents/webcomponentsjs#480 (comment) seems to be solved.
This workaround introduces yet another leyer of asynchronity, that may introduce potentially FOUC.
I think we could consider making
imported-templatetestcase based on http://tomalec.github.io/templates_vs_htmlimports-issue/, http://jsbin.com/cizeviq/edit?html,console,output, https://bugs.chromium.org/p/chromium/issues/attachmentText?aid=127035Then removing this hack.
The text was updated successfully, but these errors were encountered: