This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21489 - [Custom]: Unresolved type extended elements need a pseudo class
Summary: [Custom]: Unresolved type extended elements need a pseudo class
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 18720
  Show dependency tree / graph
 
Reported: 2013-04-01 09:25 UTC by Morrita Hajime
Modified: 2013-04-23 22:45 UTC (History)
0 users

See Also:

Attachments

Description Morrita Hajime 2013-04-01 09:25:08 UTC 
Current draft [1] defines :unknown pseudo element. 
However, it doesn't match unresolved type-extended elements like <div is=x-foo>,
which also need some style. 

One possible idea is to change :unknown to :unresolved so that
we can support both HTMLUnknownElement and type-extended node.

From custom elements perspective,
it even isn't necessary to decorate all HTMLUnknwonElement.
What we need is to decorate yet-to-be-custom unknown element
that has valid custom element name. :unresolved can only match such elements.

[1] https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html#unknown-element-pseudoclass
Comment 1 Dimitri Glazkov 2013-04-23 22:45:26 UTC 
Now that the unresolved element concept exists, this is very easy (and better):

https://dvcs.w3.org/hg/webcomponents/rev/0409b21c2588