Implement CSS :open pseudo-class
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
People
(Reporter: jarhar, Assigned: jfkthame)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: dev-doc-needed)
Attachments
(5 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36
Steps to reproduce:
Use :open in CSS
Actual results:
Selector is not matched
Expected results:
The :open CSS pseudo-class is being added to the HTML spec and will be shipped in chrome soon:
Comment 1•2 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::CSS Parsing and Computation' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Assignee | ||
Updated•2 months ago
|
Updated•22 days ago
|
Assignee | ||
Comment 2•19 days ago
|
||
Trivial doc cleanup that I noticed when going to edit this file.
Updated•19 days ago
|
Assignee | ||
Comment 3•19 days ago
|
||
This enables us to parse the pseudo, but it's not yet connected to anything.
Assignee | ||
Comment 4•19 days ago
|
||
Most of these elements are simple to support.
One slightly tricky item was <input type=date>, as testing indicates that the
front-end code usually (consistently?) hides the picker using setPickerState(),
which does not end up calling closeDateTimePicker() as might be expected.
So to properly track the open/closed state, I had to add a SetDateTimePickerState
webidl method, rather than just patching into the existing Open/Close calls.
Assignee | ||
Comment 5•19 days ago
|
||
Assignee | ||
Comment 6•17 days ago
|
||
Comment 8•15 days ago
|
||
Backed out for causing failures at select-inside-top-layer.tentative.html.
Backout link: https://hg.mozilla.org/integration/autoland/rev/a7690617e71a8713537695a0ea5d07ba443da7cb
Push with failures: https://treeherder.mozilla.org/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=2b07b9e7bf57cf8358e546b7fe4141babe72f541
Failure log: https://treeherder.mozilla.org/logviewer?job_id=490559485&repo=autoland&lineNumber=2810
Assignee | ||
Comment 10•15 days ago
|
||
(In reply to Atila Butkovits from comment #8)
Backed out for causing failures at select-inside-top-layer.tentative.html.
Backout link: https://hg.mozilla.org/integration/autoland/rev/a7690617e71a8713537695a0ea5d07ba443da7cb
Push with failures: https://treeherder.mozilla.org/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=2b07b9e7bf57cf8358e546b7fe4141babe72f541
Failure log: https://treeherder.mozilla.org/logviewer?job_id=490559485&repo=autoland&lineNumber=2810
Ah, I see.... tests involving <select> fail on android, because the widget is completely different there, and the openInParentProcess thing doesn't apply to it. I'll mark these as (still) failing for now, and file a followup bug.
Comment 12•15 days ago
|
||
Comment 13•15 days ago
|
||
Comment 14•15 days ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/afae9b8eaceb
https://hg.mozilla.org/mozilla-central/rev/27e814df42ec
https://hg.mozilla.org/mozilla-central/rev/3bfcd49c0bc8
https://hg.mozilla.org/mozilla-central/rev/6d39e75391fa
https://hg.mozilla.org/mozilla-central/rev/bd6fe64b89d7
https://hg.mozilla.org/mozilla-central/rev/0ab040b01e33
Comment 16•14 days ago
|
||
:jfkthame could you consider nominating this for a release note? (Process info)
Assignee | ||
Comment 17•14 days ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: This pseudo-class allows authors to easily target openable elements such as <details>
according to whether they are in their opened or closed state, e.g. to change the style of the Summary when a <details>
element is expanded.
[Suggested wording]: Firefox now supports the CSS :open
pseudo-class for styling elements can be toggled “open” to display more content
Comment 18•12 days ago
|
||
Thanks, added to the Fx136 nightly release notes, please allow 30 minutes for the site to update.
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx136 release notes.
Description
•