This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There should be a sane way to distinguish/style elements in their original, non-upgraded state. We don't want every component developer to roll their own attribute flag for this, as it will surely be a common case. You can approach this from two angles: a pseudo to specify an element is upgraded, :upgraded, or a pseudo for custom elements that are yet to be upgraded, :beforeupgrade. I can almost guarantee devs will write far more styles targeting the upgraded state, and mostly small visual stuff for elements that are not yet upgraded (a background spinner for instance). Not sure what route to take, thoughts?
Scott, Steve -- would love to have your ideas here.
Right now, there's http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html#unknown-element-pseudoclass. This should give you the ability to style anything that hasn't upgraded yet. For example, if you have x-foo element: x-foo:unknown <-- matches before upgrade x-foo <-- matches upgraded
(In reply to comment #2) > Right now, there's > http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index. > html#unknown-element-pseudoclass. > > This should give you the ability to style anything that hasn't upgraded yet. > For example, if you have x-foo element: > > x-foo:unknown <-- matches before upgrade > x-foo <-- matches upgraded Gosh, I must have overlooked that. In that case, the bases seem covered!
yay! *** This bug has been marked as a duplicate of bug 18534 ***