Closed
Bug 526227
Opened 16 years ago
Closed 12 years ago
Make sure we get the right container for select events
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: davidb, Unassigned)
References
Details
(Keywords: access)
We probably won't cover all cases in bug 414302, so spinning this bug off.
When we look* for the container of selectables we might want to grab the immediate parent for certain roles. This bug should try to be exhaustive for all roles that have an immediate containing parent, and we should cover these cases under automated test.
* In the soon to be named "nsAccUtils::GetSelectContainerFor"
Comment 1•12 years ago
|
||
so the method is named nsAccUtils::GetSelectableContainer now, it could be based on Accessible::Widget interface, i.e. ContainerWidget() to make this bug fixed. However ContainerWidget() must work for ARIA hierarchies (it doesn't right now). But I'm not sure whether we need to fix this bug at all. David, what is your thinking?
Reporter | ||
Comment 2•12 years ago
|
||
I've forgotten why we needed this. I'd say let's close and reopen if we find a need.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•