W3C home > Mailing lists > Public > public-html-a11y@w3.org > October 2010

[Bug 10916] Add a new <control> element to convey the common semantics of a script enabled UI control

From: <bugzilla@jessica.w3.org>
Date: Mon, 04 Oct 2010 17:58:48 +0000
To: public-html-a11y@w3.org
Message-Id: <E1P2pJI-0008OP-Ig@jessica.w3.org>

--- Comment #7 from Maciej Stachowiak <mjs@apple.com> 2010-10-04 17:58:48 UTC ---
(In reply to comment #6)
> The main use case is for editing tools. Browsers wouldn't be expected to do
> anything with the element - on the contrary they should be discouraged from
> doing anything special with the element.

What are some specific things an editing tool could do with the knowledge that
an element is a control, but without knowing anything more specific about its
behavior or semantics (since those are presumably still specific to individual
scripting libraries)?

Or, if this is meant to be used with a specific scripting library known to the
editing tool, rather than generic to any scripting library, it seems like the
scripting library and editing tool could come to a private arrangement on how
to convey this info (e.g. with data-* attributes or specific use of class

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 4 October 2010 17:58:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:46 UTC