After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 493312 - Cursor routing key doesn't update braille in FF3 adress bar
Cursor routing key doesn't update braille in FF3 adress bar
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: braille
2.20.x
Other All
: Normal normal
: FUTURE
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks: 404403
 
 
Reported: 2007-11-04 10:55 UTC by rudolf.weeber
Modified: 2008-04-04 13:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description rudolf.weeber 2007-11-04 10:55:46 UTC 
Hi,
I just found out, that the cursor routing in th FF3 adress bar does not update the braille display correctly:
1. Enter a URL
2. Press a routing key
3. Enter another character

After 2. the caret on the braille display is not updated. However, when you enter an other character or press a cursor key, this happens at the right place.
Therefore, I suspect, that the caret motion is actually carried out when pressing the routing key, but the braille display is not updated.

Cheers,
Rudolf
Comment 1 Willie Walker 2007-11-06 14:45:36 UTC 
I just confirmed this on my Solaris Express Community Edition b76 box with Orca SVN version 3218 from SVN trunk.  When one presses a cursor routing key, the caret is indeed updated on the graphical display, but it is not updated on the braille display.  To add more information, arrowing left/right on the keyboard while in the address bar does update the cursor on the braille display.
Comment 2 rudolf.weeber 2008-03-21 09:35:06 UTC 
Hi,
I just found out that this problem does not only apply to the adress bar, but also to <textarea> and <input type=text> form fieelds.

Cheers, Rudolf
Comment 3 rudolf.weeber 2008-04-04 13:21:05 UTC 
Hi,

Eitan's inclusion of cursor routing in Webpages (bug #520612) seems to have the very desirable sie effect of resolving this bug :-)

Cheers, Rudolf