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.

Sign up for GitHub

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

Jump to bottom

Provide finer control over unresolved element styling #276

Closed
sorvell opened this issue Sep 14, 2013 · 1 comment
Closed

Provide finer control over unresolved element styling #276

sorvell opened this issue Sep 14, 2013 · 1 comment
Assignees
@sorvell

Comments

@sorvell
Copy link
Contributor

sorvell commented Sep 14, 2013

This boils down to polyfilling :unresolved in some way.

Since this is difficult, in general, perhaps we can at least provide an .unresolved class which can be manually put on elements. Then polymer can remove it. Polymer would provide a default implementation of unresolved that makes the element opacity: 0.
@ghost ghost assigned sorvell Sep 14, 2013
@sorvell sorvell mentioned this issue Sep 14, 2013
Closed
@sethladd
Copy link

/sub

@ghost ghost assigned ebidel and sorvell Sep 25, 2013
sorvell added a commit that referenced this issue Sep 30, 2013
@sorvell
generalize polymer's fuoc prevention strategy; fixes: #276
24b3b3b 
 - styling is now expressed via 'polymer-veiled' and 'polymer-unveil' classes which are now user customizable.
 - to veil (initially hide) an element either include the class 'polymer-veiled' or add to the array: Polymer.veiledElements. This list includes 'body' by default but that can be removed to prevent body from getting de-fuoc'd.
 - note: Polymer automatically unveils elements at WebComponentsReady time, but elements can be dynamically unveiled by (1) adding the polymer-veiled class to them to hide them and then (2) when they are ready, calling Polymer.unveilElements().
@sorvell sorvell closed this as completed Sep 30, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sorvell sorvell

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sethladd @sorvell @ebidel