- From: Steven Faulkner <faulkner.steve@gmail.com>
- Date: Thu, 10 Sep 2009 11:38:24 +0100
- To: HTML WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
- Message-ID: <55687cf80909100338n236ce5d9j61c18f2adb3adabf@mail.gmail.com>
note that role="dialog" is already used in WAI-ARIA to indicate a dialog window. 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. regards stevef 2009/9/10 Thomas Broyer <t.broyer@ltgt.net> > On Thu, Sep 10, 2009 at 11:37 AM, Leif Halvard Silli > <xn--mlform-iua@xn--mlform-iua.no> 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 http://www.w3.org/Bugs/Public/show_bug.cgi?id=7508 ). > > > > 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ʁwa.je/ > > -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Thursday, 10 September 2009 10:39:09 UTC