256249 - Mozilla main window (frame) should have an accessible name

Status: RESOLVED WORKSFORME

(Core :: Disability Access APIs, defect)

Description

[Dana Ormenisan]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040726
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040726

1. Open mozilla
2. Open gnopenricus
3. Switch to mozilla window => the name of this window is not reported
4. Check with at-poke

Reproducible: Always
Steps to Reproduce:

Actual Results:  
This frame does not have an accessible name. 

Expected Results:  
This frame should have an accessible name.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 3

[Bill Haneman]

REOPENING.

This bug expiry thing is a major PITA 

Comment 4

[Evan Yan]

can't be reproduced in the latest trunk build.
It seems has been fixed by some other patch.