Re: [Bug 7509] Consider <dl type="dialog"> instead of <dialog>

note that role="dialog" is already used in WAI-ARIA to indicate a dialog
if the <dialog> element continues to be in HTML 5, it would be sensible for
it to be used as structural container for content that represents a scripted
dialog window. This is a use case that has many applications, far more i
would suggest than its current defined use.


2009/9/10 Thomas Broyer <>

> On Thu, Sep 10, 2009 at 11:37 AM, Leif Halvard Silli
> <> wrote:
> >> Yeah, but there's also the floating idea that the content model of
> >> <dialog> could evolve later to allow "non-speech related information"
> >> (see ).
> >
> > Bug 7508 is very inspired by how <dl> is defined ...
> >
> >> This doesn't (a priori) concern key-value lists though, which could
> >> therefore use a typed-<dl> instead of minting a new element.
> >
> > What is it that (a priori) makes it better to have a <dialog> element
> rather
> > than a typed - or "roled" - <dl> element? I see nothing.
> Having a content model that depends on the value of an attribute is
> something we should avoid; and that's something that would appear, if
> we use <dl role=dialog> instead of <dialog>, as soon as we start
> adding non-speech related information to a dialog (and make it
> non-conforming for a list of definitions and/or a key-value list).
> --
> Thomas Broyer
> /tɔ.ma.bʁ

with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium |
Web Accessibility Toolbar -

Received on Thursday, 10 September 2009 10:39:09 UTC