Magnifier (gnome-mag) doesn't get focus in firefox

[Aurelian Radu]

Install gnopernicus, gnome-mag. Enable accessibility support (with magnifier option checked). Open gnopernicus and firefox. Type anything in the firefox address bar or upper-right corner search box. Magnifier doesn't get focus to where you type. Focus jumps to the upper-left corner of the screen. The same happens when typing in any web page. Exception: on Gmail and Yahoo! Mail login pages, magnifier gets focus ONLY for the password field, not the User/Email field. In ubuntuforums, when trying to reply using the quick reply button, gnome-mag does not react: focus stays on the mouse pointer. But if you click on "Switch Editor Mode" button in the upper-right corner of the reply field and then type your reply, magnifier focus jumps to the upper-left corner of the screen.

[Reed Loden (reed)]

(In reply to comment #0)
> Could you create another category for Accessibility?

We have a "Disability Access" component that this would fall under. Moved to it.

[Ginn-chen (ginn-chen)]

Like a dupe of bug 172674

[Evan Yan (evan-yan)]

Created attachment 205718
deal with the situation when there is no text to get

this bug is caused by two things:
1. In nsMaiInterfaceText.cpp:getCharacterExtentsCB, it should be "if(!accText)" but not "if(accText)". This has been fix by some patch from Ginn Chen for another bug.
2. When user deleted all the text in a text box, nsAccessibleText::GetCharacterExtents() will end with error, Which the attached patch deals with.

[Jason Grieves (jasongrieves)]

(In reply to comment #3)

Thanks so much! This bug does a much better job keeping up with me. However as I type this bug in this box, it does not bring hte focus back correctly when it reaches the end of a line. Instead it appears to out of bounds and loses focus completely. The product is much more usable however to the gnome-mag screen magnifier.

> Created an attachment (id=205718) [edit]
> deal with the situation when there is no text to get
>
> this bug is caused by two things:
> 1. In nsMaiInterfaceText.cpp:getCharacterExtentsCB, it should be "if(!accText)"
> but not "if(accText)". This has been fix by some patch from Ginn Chen for
> another bug.
> 2. When user deleted all the text in a text box,
> nsAccessibleText::GetCharacterExtents() will end with error, Which the attached
> patch deals with.
>

[Evan Yan (evan-yan)]

I think that is another bug. And I filed bug 320357 for that.

(In reply to comment #4)
> Thanks so much! This bug does a much better job keeping up with me. However
> as I type this bug in this box, it does not bring hte focus back correctly when
> it reaches the end of a line. Instead it appears to out of bounds and loses
> focus completely. The product is much more usable however to the gnome-mag
> screen magnifier.
>

[Aaronleventhal (aaronleventhal)]

How can this fix anything for ZoomText if the patch is only in the atk directory? That's not built for Windows.

[Evan Yan (evan-yan)]

In fact, I have tested the bug under windows, and can reproduce it.

User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

[Evan Yan (evan-yan)]

sorry for the typo.
I can NOT reproduce the bug under windows.

(In reply to comment #7)
> In fact, I have tested the bug under windows, and can reproduce it.
>
> User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8)
> Gecko/20051111 Firefox/1.5
>

[Ginn-chen (ginn-chen)]

Jason, can reproduce this bug with latest trunk and Zoomtext on Windows?

[Ginn-chen (ginn-chen)]

Checking in nsAccessibleText.cpp;
/cvsroot/mozilla/accessible/src/atk/nsAccessibleText.cpp,v <-- nsAccessibleText.cpp
new revision: 1.26; previous revision: 1.25
done

[Jason Grieves (jasongrieves)]

(In reply to comment #9)
> Jason, can reproduce this bug with latest trunk and Zoomtext on Windows?
>
I believe this is fixed in the latest trunk and latest Zoomtext. I have contacted a fellow Zoomtext user who will open a new bug if he experienced any other problems.

Thanks for the fix!

[Ginn-chen (ginn-chen)]

Comment on attachment 205718
deal with the situation when there is no text to get

Firefox is unusable with gnome magnifier when trying to inputs something.

Risk is low.

See also Bug 317482

[Ginn-chen (ginn-chen)]

Checking in src/atk/nsAccessibleText.cpp;
/cvsroot/mozilla/accessible/src/atk/nsAccessibleText.cpp,v <-- nsAccessibleText.cpp
new revision: 1.24.8.1; previous revision: 1.24
done

[Aurelian Radu (linbetwin)]

Install gnopernicus, gnome-mag. Enable accessibility support (with magnifier option checked). Open gnopernicus and firefox. Type anything in the firefox address bar or upper-right corner search box. Magnifier doesn't get focus to where you type. Focus jumps to the upper-left corner of the screen. The same happens when typing in any web page. Exception: on Gmail and Yahoo! Mail login pages, magnifier gets focus ONLY for the password field, not the User/Email field. In ubuntuforums, when trying to reply using the quick reply button, gnome-mag does not react: focus stays on the mouse pointer. But if you click on "Switch Editor Mode" button in the upper-right corner of the reply field and then type your reply, magnifier focus jumps to the upper-left corner of the screen.

[Aurelian Radu (linbetwin)]

I know there's a bug filed by Jason Grieves in the Mozilla Bugzilla and I think one of the developers provided a fix, but the fix didn't make it into Dapper yet.

[Phil Bull (philbull)]

Do you have a link to that bug, Aurelian?

[Aurelian Radu (linbetwin)]

Thank you for replying, Phil! Here is the link:

https://bugzilla.mozilla.org/show_bug.cgi?id=317213

This bug is present in all versions of Firefox and gnome-mag/gnopernicus, on all disrtibutions I've tested (Ubuntu 5.04, 5.10, 6.06, SUSE 10.0, Mandrakelinux 10.2, Mandriva 2006.0, FC 5, etc.). Firefox is not 100 % accessible in Windows either (using the Windows magnifier, not ZoomText) but it's really unusable with gnome-mag/gnopernicus under Linux.

[Phil Bull (philbull)]

Thanks for the reply, I'm confirming the bug.

[David Farning (dfarning)]

Is this still an issue? Upstream is reporting it as fixed as if Feb of 2006.

Thanks
David

[John Vivirito (gnomefreak)]

Thank you for the bug report. However I haven't heard back from you in 30 days. We are now going to close this report - please reopen if necessary when you have more information at hand.