Closed
Bug 327396
Opened 18 years ago
Closed 18 years ago
Items in Places results list do not have accessible names
Categories
(Firefox :: Bookmarks & History, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 246236
Firefox 3
People
(Reporter: pilgrim, Unassigned)
References
Details
(Keywords: access)
Attachments
(1 file)
87.34 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060214 Firefox/1.6a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060214 Firefox/1.6a1 Note: this is not always reproducible. Sometimes all of the items work as expected, sometimes none of them work as expected. Once -- I am not making this up -- the first 8 items in the list showed blank accessible names, and starting at item 9 the accessible names were correct (but arrowing back up to item 8 still showed a blank accessible name). Reproducible: Sometimes Steps to Reproduce: 1. Open Inspect32 2. Open Places 3. Search for something within your history/bookmarks 4. Tab to results list 5. Inspect32 shows item's accessible name = " " 6. Arrow up and down to see identical results for other items in results list Actual Results: Accessible name is blank Expected Results: Accessible name is combination of all columns in selected row of results pane (page title + URL + visited date + page count)
Updated•18 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 1•18 years ago
|
||
Updated•18 years ago
|
Assignee: nobody → brettw
Priority: -- → P2
Target Milestone: --- → Firefox 2 alpha2
Comment 3•18 years ago
|
||
Mark, do you know how I provide an accessible name for an instantiation of a XUL widget? or XBL binding?
Comment 4•18 years ago
|
||
This appears to be a problem with the widget itself. I belive Hans Hillen was saying that we expose the wrong thing in tree views when the contents change. Must be that the cache isn't getting invalidated.
Assignee: brettw → pilgrim
Severity: normal → major
Priority: P3 → P2
Comment 5•18 years ago
|
||
(In reply to comment #4) > This appears to be a problem with the widget itself. I should say, with the mozilla/accessible implementation of accessibility for the widget.
Comment 6•18 years ago
|
||
This could be the same as bug 328273. I think we're not invalidating the accessible object cache when a tree object changes.
Reporter | ||
Updated•18 years ago
|
Target Milestone: Firefox 2 alpha2 → Firefox 3
Reporter | ||
Updated•18 years ago
|
Assignee: pilgrim → nobody
Comment 7•18 years ago
|
||
This is almost certainly a dupe of bug 246236 which is fixed in the latest nightly builds.
Comment 8•18 years ago
|
||
Is this still broken after the checkin for bug 246236?
Updated•18 years ago
|
Blocks: fox2access
Comment 9•18 years ago
|
||
*** This bug has been marked as a duplicate of 246236 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Comment 10•15 years ago
|
||
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h". In Thunderbird 3.0b, you do that as follows: Tools | Message Filters Make sure the correct account is selected. Click "New" Conditions: Body contains places-to-b-and-h Change the action to "Delete Message". Select "Manually Run" from the dropdown at the top. Click OK. Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter. Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in
before you can comment on or make changes to this bug.
Description
•