GNOME Bugzilla – Bug 171583
wrong text report to brlmon
Last modified: 2005-04-01 16:58:03 UTC
Run Swing Demo. Choose 'TextArea Two'. Start gnopernicus with braille monitor on. Move through the objects from 'TextArea Two' tag. The carret on the braille monitor has allways a wrong offset for the text objects.
Created attachment 39238 [details] [review] Proposed patch Proposed patch to prevent the case described in bug #171581.
Created attachment 39331 [details] [review] reworked patch
The previous patch is not the wanted one.
Created attachment 39334 [details] [review] Proposed patch
The problem is general and a workaround can't be done in gnopernicus. *** This bug has been marked as a duplicate of 171581 ***
Oana, does gnopernicus ignore the caret position as reported by at-spi? Or is the text-caret position also wrong?
brlmonitor works correctly with StylePad using the latest java-access-bridge. What is different about the 'swing demo'? Can you provide another example of a Java application in which this doesn't work correctly? It all appears to be correct to me.
I tried Swing Demo also, and it works fine for me. I am running java 1.5.0_01-b06.
I am running java 1.5.0_01-b08. In Swing Demo, for 'Text Fields' tab (for example), if I move to the text box which contains the explanation for this example, on the braille monitor the text is: "This example shows the.....". The carret position on the braille is correct. If you move to the next line, on the braille the text reported is: "_fields. The accessible.....", where "_" means <space> (the text should be without that <space>). This happens because the line start is not good (the line start reported, in this case, is the good value - (minus) 1). And the carret is on the second position on the braille monitor.
Thanks Oana; I've seen the 'extra space' here as well. If this is the only manifestation of the problem (extra space at beginning of line), then this is a less severe bug than 171581.
*** This bug has been marked as a duplicate of 171581 ***