Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FOUC body[unresolved] should be [unresolved] #431

Closed
ebidel opened this issue Feb 24, 2014 · 3 comments
Closed

FOUC body[unresolved] should be [unresolved] #431

ebidel opened this issue Feb 24, 2014 · 3 comments

Comments

@ebidel
Copy link
Contributor

ebidel commented Feb 24, 2014

The [unresolved] attribute is no longer available for use on single elements. It's only applicable to body now:

screen shot 2014-02-24 at 2 32 14 pm

This means apps have less flexibility when it comes to controlling their own FOUC. Why did we change to just body?

@sjmiles
Copy link
Contributor

sjmiles commented Feb 24, 2014

You can still put unresolved attribute on any custom element and the polyfill will remove that attribute when the element is upgraded. We leave it up to the developer to decide how to use that information.

We have special sauce for body just because it provides an easy solution for simple pages.

@ebidel
Copy link
Contributor Author

ebidel commented Feb 24, 2014

Thanks for clarifying. A quick heads up on changes like this would be good. Keeps our docs from getting stale every week :)

@ebidel
Copy link
Contributor Author

ebidel commented Feb 24, 2014

Updated the docs.

@ebidel ebidel closed this as completed Feb 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants