Closed
Bug 380848
Opened 18 years ago
Closed 17 years ago
Selected list item is not reported when focus to the list
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: tim.miao, Assigned: evan.yan)
References
Details
(Keywords: access)
Attachments
(1 file, 1 obsolete file)
1.30 KB,
patch
|
neil
:
review+
damons
:
approval1.9+
|
Details | Diff | Splinter Review |
Steps to reproduce:
1. Launch orca and thunderbird.
2. Invoke address book import wizard dialog.
3. In second dialog window of import wizard, by default, when this window was firstly brought up, orca will report table list of supported file type.
4. Press Tab to move focus away from this table list item, then move focus back.
Expected result:
Table list should be reported.
Actual result:
It will not be reported when you move focus onto it for second time.
Additional info:
This bug can be found with thunderbird 20070515 trunk nightly build.
If I change focus between windows, Orca will read the texts in the wizard dialog. There is window:active event when changing focus on windows.
For static texts that not label for any controls, which event does Orca depend to read them? just window:active event?
sorry, wrong comment, comment #1 is meant for bug 380695
When the second page first brought up, there is a focus event fired on the list item, when tab to the list, focus event is fired on the list, but not on the list item. That's why Orca won't read the item.
Should we fire focus event for the selected list item when focus to the list?
Assignee: mscott → aaronleventhal
Component: General → Disability Access APIs
OS: SunOS → Linux
Product: Thunderbird → Core
QA Contact: general → accessibility-apis
Summary: Table list item is not reported if user tabs focus onto it after first time accessing. → Selected list item is not reported when focus to the list
In addition, the file type list should be labeled by its above text, bug 381389 filed for this.
I guess the problem here is, if the list only has one listitem, you could not focus it.
Comment 6•18 years ago
|
||
I just checked in a fix for a big regression in nsXULTreeAccessible, does that fix this bug?
The fix was in bug 380976.
Updated•18 years ago
|
Assignee: aaronleventhal → Evan.Yan
To Ginn, there is only one list item, but it was selected by default, you could tab focus onto it.
To Aaron, I will verify this bug later today and give update once I got the trunk build with your fix.
This bug is still visible with thunderbird 3.0a1pre(20070523) build.
The first time the page show up, there is focus event fired for the list item, that's because there is DOMMenuItemActive event fired for the list item.
As Ginn mentioned in comment #5, when list only has one listitem, it will never be focused. So I think the answer to comment #3 is yes.
Assignee | ||
Comment 10•18 years ago
|
||
Actually, we have tried to fire focus event for the selected item, in nsRootAccessible::HandleEventWithTarget() handling "focus" event.
However, it seems a listitem was set as selected AFTER "focus" event comes to listbox. When handling "focus" event, selectControl->GetSelectedItem() returns null.
What's more, we didn't deal with HTML list.
Assignee | ||
Comment 11•17 years ago
|
||
We fired DOMMenuItemActive when currentItem is set. But when focus to a xul listbox, listitem is focused and selected without currentItem get changed. So focus event on listitem is missed in this case.
The situation gets worse when a listbox has only one listitem. There will never be a focus event on the listitem.
Attachment #289795 -
Flags: review?(mconnor)
Assignee | ||
Comment 12•17 years ago
|
||
Comment on attachment 289795 [details] [diff] [review]
fire DOMMenuItemActive when focus to listbox
Neil, could you help review this patch, since you were in a discussion of a similar issue in bug 381602?
It's just three lines change.
Attachment #289795 -
Flags: review?(neil)
Comment 13•17 years ago
|
||
Comment on attachment 289795 [details] [diff] [review]
fire DOMMenuItemActive when focus to listbox
This will error on an empty listbox. It's probably best to reverse the logic, so you test for a current item first, otherwise you test for an empty list second.
Attachment #289795 -
Flags: review?(neil) → review-
Assignee | ||
Comment 14•17 years ago
|
||
Thanks for the quick review, here is the updated patch.
Attachment #289795 -
Attachment is obsolete: true
Attachment #291814 -
Flags: review?(neil)
Attachment #289795 -
Flags: review?(mconnor)
Assignee | ||
Comment 15•17 years ago
|
||
mark as block bug 396346, because it makes never a focus event on the only listitem in a listbox.
Blocks: fox3access
Comment 16•17 years ago
|
||
Comment on attachment 291814 [details] [diff] [review]
patch v2
OK, I guess this version is more readable than what I was thinking of.
Attachment #291814 -
Flags: review?(neil) → review+
Attachment #291814 -
Flags: approval1.9?
Comment 17•17 years ago
|
||
Comment on attachment 291814 [details] [diff] [review]
patch v2
a=endgame drivers.
Attachment #291814 -
Flags: approval1.9? → approval1.9+
Assignee | ||
Comment 18•17 years ago
|
||
/cvsroot/mozilla/toolkit/content/widgets/listbox.xml,v <-- listbox.xml
new revision: 1.32; previous revision: 1.31
done
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•