Repository navigation
[0.8] body unresolved broken #1271
Description
Activity
In webcomponents/webcomponentsjs#230 I've proposed a workaround which solved that issue for me. But it was classified as not being ok.
Running into this too
Confirmed that I've been bitten by this too, but I agree with @garlicnation's resolution on that bug. It's fine for the framework or user to remove the unresolved attribute at a time they consider the page ready.
I've a page with several components. I've no problem to remove unresolved myself - but how do I know that all components are ready and won't cause any FOUC?
@addyosmani,
unresolvedwas always something users had to manage themselves if they were just using the wc.js polyfill (though IIRC, there was a time before when wc.js did this too). If authoring 0.5 Polymer elements,unresolvedwas removed by Polymer as a sugaring feature.Id would be best if the
webcomponents.jspolyfills would take care of this issue, but doing so would break support for Polymer 0.5. That said, it seems reasonable and simple for Polymer to auto-remove this attribute at the appropriate time.
To prevent FOUC we used, as suggested,
<body unresolved>. webcomponents.js always define the style for unresolved - so the body still gets hidden.But it seems that in 0.8 the
unresolvedis never removed from body.If I don't use unresolved I see the page but again get FOUC in FF & IE.