Closed
Bug 1867785
Opened 2 years ago
Closed 1 month ago
[invokers] Move details invokeaction under new flag
Categories
(Core :: DOM: Core & HTML, task)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
142 Branch
Tracking | Status | |
---|---|---|
firefox142 | --- | fixed |
People
(Reporter: lwarlow, Assigned: keithamus)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
OpenUI have agreed on a v1 for invokers that includes just the actions for popover and dialog. So any extra actions that are implemented such as details should be moved under a separate flag.
Assignee | ||
Updated•1 year ago
|
Assignee: nobody → mozilla
Summary: Move details invokeaction under near flag → Move details invokeaction under new flag
Assignee | ||
Updated•1 year ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•1 year ago
|
Summary: Move details invokeaction under new flag → [invokers] Move details invokeaction under new flag
Reporter | ||
Comment 1•6 months ago
|
||
We should maybe just remove the details implementation for now (as it's possible/probably it never ships)?
Assignee | ||
Comment 2•2 months ago
|
||
These commands are not spec compliant, but are proposed features in the
"future commands" proposal under Open-UI. As they're not spec compliant,
they should only be exposed flagged.
(https://open-ui.org/components/future-invokers.explainer/)
Pushed by mozilla@keithcirkel.co.uk:
https://github.com/mozilla-firefox/firefox/commit/e97372a84926
https://hg.mozilla.org/integration/autoland/rev/fed4ec313f4d
Move details commandfor commands behind flag r=dom-core,edgar
Comment 4•1 month ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
status-firefox142:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Updated•27 days ago
|
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in
before you can comment on or make changes to this bug.
Description
•