Closed Bug 1253086 Opened 8 years ago Closed 7 years ago

Unresolved Pseudo Selector Broken

Categories

(Core :: DOM: Core & HTML, defect)

43 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jshcrowthe, Assigned: edgar)

References

Details

(Keywords: testcase, Whiteboard: btpp-followup-2016-03-10)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36

Steps to reproduce:

- Implement a stylesheet that uses the component-name:unresolved pseudo selector for custom elements
- Register a custom element by the same name
- Can also be seen by viewing the following URL in Firefox: http://w3c-test.org/custom-elements/registering-custom-elements/unresolved-element-pseudoclass/unresolved-element-pseudoclass-matching-query-selector.html


Actual results:

The :unresolved pseudo selector targets the resolved web component


Expected results:

The :unresolved pseudo selector should cease to target a resolved web component.
Keywords: testcase
Product: Firefox → Core
Component: Untriaged → DOM
I don't know if our implementation is ready for this yet but I could be mistaken or misunderstanding. William?
Flags: needinfo?(wchen)
Whiteboard: btpp-followup-2016-03-10
Any word on this?
Apparently :unresolved has been removed in favour of :defined (a bit different, I guess): https://w3c.github.io/webcomponents/spec/custom/#unresolved-element-pseudoclass .

Edgar is working on Custom Elements so is probably interested in having this tracked (I'll let him put it into the right dependency tree).
Flags: needinfo?(wchen) → needinfo?(echen)
Set the dependency to the meta bug for the new implementation. And we will make sure :defined selector work well with new stuff.
Flags: needinfo?(echen)
And we are going to remove :unresolved in bug 1417829.
Close as INVALID given that :unresolved has been removed in bug 1417829.
Please see bug 1331334 to get more detailed status for :defined.
Thank you.
Assignee: nobody → echen
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.