W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default

From: <bugzilla@jessica.w3.org>
Date: Thu, 13 Jan 2011 14:28:26 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PdOA6-0007rt-2C@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11557

--- Comment #19 from Henri Sivonen <hsivonen@iki.fi> 2011-01-13 14:28:25 UTC ---
(In reply to comment #18)
> (In reply to comment #16)
> > (In reply to comment #15)
> > > as implemented in any case where an author wishes make use of a state or
> > > property that is particular to a role
> > > example: aria-pressed on the button role the role needs to be explicitly added.
> > > 
> > > <input type=button role='button" aria-pressed=true>
> > 
> > What's the use case for overriding the pressed state on type=button?
> > type=button has been supported natively for a long time.
> 
> Indicates the current "pressed" state of toggle buttons. 
> http://www.w3.org/WAI/PF/aria/states_and_properties#aria-pressed

In that case, your example looks like an abuse of type=button to me, since
type=button isn't a toggle button. How would you make type=button make look
like one visually?

> there are no native toggle buttons in HTML or am I missing something?

The closest HTML has natively is checkboxes and radiobuttons.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 13 January 2011 14:28:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 14:28:28 GMT