[meta] Implement the HTML5 dialog element
Categories
(Core :: DOM: Core & HTML, enhancement)
Tracking
()
People
(Reporter: dmh, Unassigned)
References
(Depends on 2 open bugs, Blocks 4 open bugs)
Details
(5 keywords, Whiteboard: [devRel:P2])
Attachments
(1 file, 1 obsolete file)
4.86 KB,
text/html
|
Details |
Comment 1•12 years ago
|
||
Reporter | ||
Updated•12 years ago
|
Reporter | ||
Updated•12 years ago
|
Reporter | ||
Comment 2•12 years ago
|
||
Comment 3•11 years ago
|
||
Updated•11 years ago
|
Comment 4•11 years ago
|
||
Updated•11 years ago
|
Comment 5•11 years ago
|
||
Updated•10 years ago
|
Reporter | ||
Comment 6•10 years ago
|
||
Comment 7•10 years ago
|
||
Updated•10 years ago
|
Comment 10•9 years ago
|
||
Comment 11•8 years ago
|
||
Comment 12•8 years ago
|
||
Updated•8 years ago
|
Comment 13•8 years ago
|
||
Updated•8 years ago
|
Updated•8 years ago
|
Comment 14•8 years ago
|
||
Updated•8 years ago
|
Comment 15•8 years ago
|
||
Comment 16•8 years ago
|
||
Comment 17•8 years ago
|
||
Comment 18•8 years ago
|
||
Updated•8 years ago
|
Comment 19•8 years ago
|
||
Comment 20•8 years ago
|
||
Comment 21•8 years ago
|
||
Comment 23•7 years ago
|
||
Comment 24•7 years ago
|
||
Comment 26•7 years ago
|
||
Comment 27•7 years ago
|
||
Comment 28•7 years ago
|
||
Comment 29•7 years ago
|
||
Comment 30•7 years ago
|
||
Comment 31•6 years ago
|
||
Updated•6 years ago
|
Comment 32•6 years ago
|
||
Comment 33•6 years ago
|
||
Comment 34•6 years ago
|
||
Comment 35•6 years ago
|
||
Comment 36•6 years ago
|
||
Comment 37•6 years ago
|
||
Updated•6 years ago
|
Comment 38•6 years ago
|
||
I just discovered <dialog>
today. It would solve a specific problem I have with my Web app perfectly. (My particular concern is solved by the "pending dialog” stack to handle the case of multiple modal dialogs.) I would love to see this implemented and am now worried about it being removed from the HTML spec due to only Chrome implementing it. Please prioritize this accessibility feature and affirm this feature's presence in the HTML spec.
Updated•6 years ago
|
Comment 39•5 years ago
|
||
Moving to DOM to reflect correct ownership.
Comment hidden (advocacy) |
Comment 41•5 years ago
|
||
The priority for this bug is not set yet. :hsinyi can you or somebody of your team set it, please?
Sebastian
Comment 42•5 years ago
|
||
(In reply to Sebastian Zartner [:sebo] from comment #41)
The priority for this bug is not set yet. :hsinyi can you or somebody of your team set it, please?
Meta bugs generally shouldn't be prioritized.
Comment 43•5 years ago
|
||
As Matthew explained, meta bugs usually don't get prioritized as well as a new feature request (enhancement type) which will go to our planning queue with PM.
Comment hidden (advocacy) |
Comment 45•5 years ago
|
||
(In reply to Hsin-Yi Tsai [:hsinyi] from comment #43)
As Matthew explained, meta bugs usually don't get prioritized as well as a new feature request (enhancement type) which will go to our planning queue with PM.
Should someone create a new feature request for it? Happy to do so if that will help move this along.
Updated•5 years ago
|
Comment 47•4 years ago
|
||
This bug is 7 years old. I love to see this supported without flags, as it is in Chromium. I'd use this a lot if Firefox would support it too.
Comment 48•4 years ago
|
||
I use a <dialog> element for my web application, but I obviously want to support as many browsers as possible. Is this the current alternative?
https://github.com/niutech/showModalDialog
My apologies if there's a well-known way to do modals in Firefox that I'm unaware of.
Comment 49•4 years ago
|
||
Hi Jesse, showModalDialog
is considered deprecated, and support for it was removed from Chrome 43 and Firefox 56, see: https://developer.mozilla.org/en-US/docs/Web/API/Window/showModalDialog
This bug report is only about the <dialog>
HTML element and comments should be restricted to that.
Comment 50•4 years ago
|
||
Hi David,
Thanks for the response. Sorry if I was unclear. What I meant was that I'm not sure what the standard alternative to the <dialog> element is.
Comment 51•4 years ago
|
||
In case anyone else is in the situation I was in, this is what I used:
https://github.com/GoogleChrome/dialog-polyfill
It worked perfecly.
Comment 52•4 years ago
|
||
I've noticed the <dialog> element appears to now be enabled by default in Nightly, but it's incompatible with our PWA. I filed issue 1656874 about that.
Comment 53•4 years ago
|
||
In case it helps, I tested the Chrome <dialog>
demo in FF Nightly and it seems to work fine. Looking forward to seeing this land in general FF!
Comment 54•4 years ago
|
||
I look forward to this too!
Comment 55•4 years ago
|
||
Is there any estimate of when this will be enabled in general releases?
We have some internal new UI for Thunderbird where we could make use of it if it's stable enough...
Comment 56•4 years ago
|
||
There are a couple minor spec issues but it's always enabled for chrome code anyways, iirc.
Comment 57•3 years ago
|
||
Hello, I find a inner-state bug when combine <dialog>
and CSS filter
:
- an
<dialog>
is under an element havingstyle="filter: invert(1);"
- the dialog has a child element with
position: fixed
- call
dialog.showModal()
- then the child element with
position: fixed
will not be fixed, but act somehow like "position: absolute" - if use JS to modify its styles to
position: absolute
and then rollback, then the newposition: fixed
will work as expected.
Here's my test demo: https://jsfiddle.net/rvnz4q9e/
I've tested Firefox 90, 91.0esr, and 93 nightly.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 58•3 years ago
|
||
It's been enabled by default as per bug 1733536.
Updated•3 years ago
|
Comment 59•3 years ago
•
|
||
Hsin-Yi Tsai (triage owner), could you ask someone to comment on this bug?
(Thunderbird) Bug 1754094 - (Modal) HTML5 dialogs do not contain their tab sequence - cycles dozens of window stops before returning to the dialog
Per https://www.w3.org/TR/wai-aria-practices/#dialog_modal, (modal) dialogs must contain their tab sequence, i.e. pressing tab must cycle only within the dialog.
Comment 60•3 years ago
|
||
(In reply to Thomas D. (:thomas8) from comment #59)
Hsin-Yi Tsai (triage owner), could you ask someone to comment on this bug?
Bug 1754094 - (Modal) HTML5 dialogs do not contain their tab sequence - cycles dozens of window stops before returning to the dialog
Per https://www.w3.org/TR/wai-aria-practices/#dialog_modal, (modal) dialogs must contain their tab sequence, i.e. pressing tab must cycle only within the dialog.
Sure thing.
Emilio and Sean have been working on this feature. Let's start from them.
Comment 61•3 years ago
|
||
That seems a bug about thunderbird, what am I missing? Modal dialogs trap focus from the pages point of view (makes everything else on the page inert). But we don't want to prevent the user from interacting with the browser chrome just because a page has called dialog.showModal, that'd be pretty user hostile.
Thunderbird can use dialog and it'd trap focus like dialogs trap focus on Firefox. Again, i feel like I'm missing something.
Comment 62•3 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #61)
That seems a bug about thunderbird, what am I missing? Modal dialogs trap focus from the pages point of view (makes everything else on the page inert). But we don't want to prevent the user from interacting with the browser chrome just because a page has called dialog.showModal, that'd be pretty user hostile.
Thunderbird can use dialog and it'd trap focus like dialogs trap focus on Firefox. Again, i feel like I'm missing something.
https://github.com/w3c/aria-practices/issues/1772 is the relevant discussion about whether to prevent access to the browser chrome while a modal dialog is open.
Comment 63•11 months ago
•
|
||
Hi Dennis, is there a still reason that we think this "meta" bug is webcompat:P2, especially given that <dialog> was enabled already in bug 1733536?
Comment 64•11 months ago
|
||
Sorry, Hsin-Yi, I somehow missed your ni? :) I don't think we have any known active breakage on this (also supported by the fact that we don't have a Knowledge Base bug for this), but I've flagged this for next Monday's triage meeting so I can sync with the others about this.
Keeping my ni? active until then.
Comment 65•11 months ago
|
||
Doesn't seem like this is a WebCompat issue anymore, so unsetting the flag.
Comment 66•1 month ago
|
||
Since Dialog is enabled by default, should this still be open?
Comment 67•1 month ago
|
||
(In reply to Randell Jesup [:jesup] (needinfo me) from comment #66)
Since Dialog is enabled by default, should this still be open?
The intent of this meta bug seemed to change a bit that the feature was enabled. That is, this is used to track defects of the <dialog> implementation, like bug 1841338 and bug 1841339. However, I am fine with closing this one and if helpful, creating a new meta to track defects.
Updated•10 days ago
|
Description
•