20186 2012-11-30 18:06:33 +0000 [Custom]: Add a CSS pseudo to distinguish between upgraded, custom elements 2012-12-10 20:30:47 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified All All RESOLVED DUPLICATE 18534 P2 normal --- 14968 1 danieljb2 dglazkov sjmiles sorvell public-webapps-bugzilla oldest_to_newest 79198 0 danieljb2 2012-11-30 18:06:33 +0000 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? 79306 1 dglazkov 2012-12-03 17:33:55 +0000 Scott, Steve -- would love to have your ideas here. 79307 2 dglazkov 2012-12-03 17:35:32 +0000 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 79309 3 danieljb2 2012-12-03 17:43:10 +0000 (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! 79857 4 dglazkov 2012-12-10 20:30:47 +0000 yay! *** This bug has been marked as a duplicate of bug 18534 ***