Hi, I'm currently working on improving a focus tracking zoom for compiz, that I hope to be soon released upstream (ubuntu) and in debian, which would add to the a11y of desktops for visually impaired. The treatment of text objects in libatspi2 is well done, however with minor drawbacks for visual applications. One of which is caret management on limit cases. When caret is on a newline, it is quite hard to get the screen position of the newline/caret, making it hard to track for a zoom. The function atspi_text_get_character_extents is of no help, and returns 0,0 as coordinates when such offset is provided. Another similar little bother is when a text is empty, thereby no text offset is present. The zoom area should then be on the caret, so one can see one can start typing. However, is it to my knowledge impossible to get a character extents, or a caret position/size of some kind. I know some of these behaviors are probably correct according to AT-SPI standard, but is it voluntary? Has this problem ever surfaced in other applications? Is it possible to do some extra functions? Last question is, how does orca manage these issues? Or does the problem just not occur? I take any workaround present in people's minds. Thanks for reading. -- Ksamak
Attachment:
pgpzZmOEwAwD9.pgp
Description: PGP signature