Closed
Bug 389238
Opened 17 years ago
Closed 14 years ago
Support disabled state on fieldset
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
mozilla2.0b7
People
(Reporter: aaronlev, Assigned: davidb)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Quoted from Bz in various bugs:
Whenever the fieldset disabled stuff is implemented, all the places that look
at "disabled" attributes (e.g. accessibility, native theme stuff, etc) will
need to be fixed to look at content states instead.
... it would make most sense for you to look for the disabled
state (which can depend on the disabled attribute on the node itself, or on
other parts of the DOM; for example in Web Forms 2, all form elements inside a
disabled fieldset are automatically disabled, even though they don't have
"disabled" attributes) and explicitly look for the ARIA attribute only here.
My note: make sure XUL disabled state still works
|
||
Comment 1•17 years ago
|
||
(note for me: bug where states will be used too is bug 388133).
I wonder do states work already? And do they work for xforms?
|
Assignee | |
Comment 2•15 years ago
|
||
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
|
||
Comment 3•14 years ago
|
||
disabled attribute for fieldset element is currently supported by IE 6+ (parity-ie) and Opera 9.27+ (parity-opera).
|
|
||
Comment 4•14 years ago
|
||
Never mind. The bug #557087 resolved just three days ago has fixed the issue. This bug probably should be closed too.
|
|
Assignee | |
Comment 6•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•14 years ago
|
Flags: in-testsuite+
Target Milestone: --- → mozilla2.0b8
|
||
Updated•14 years ago
|
Target Milestone: mozilla2.0b8 → mozilla2.0b7
You need to log in
before you can comment on or make changes to this bug.
Description
•