Problem description
For offset based TextInfos (like IAccessible2), it is possible to retrieve a point for a specific offset. This allows the move mouse to navigator object script to move the mouse to the exact point that a character takes on screen.
For non offsets based text infos, it is currently not possible to fetch this information. Currently, I think that UIA text info is the most important case where this functionality is lacking.
Proposed solution
It looks like UIA exposes a bounding rectangle for every character of a text range. The display model also exposes a bounding rectangle for every character and calculates a point from that rectangle. I'm pretty sure that IAccessible2 implements per character bounding rectangles as well.
Therefore, I propose an additional boundingRectangle property on textInfo objects that calculates the bounding rectangle of the current text range. This should be pretty easy when we use locationHelper (#7537). This will also allow us to implement de pointAtStart property for UIATextInfo, in which case moving the mouse to the current review position should be much more accurate. It would also allow detailled tracking of the browse mode position in Microsoft Edge and Microsoft Word with UIA enabled, that is, if both of them implement this properly.
cc @michaelDCurran
Problem description
For offset based TextInfos (like IAccessible2), it is possible to retrieve a point for a specific offset. This allows the move mouse to navigator object script to move the mouse to the exact point that a character takes on screen.
For non offsets based text infos, it is currently not possible to fetch this information. Currently, I think that UIA text info is the most important case where this functionality is lacking.
Proposed solution
It looks like UIA exposes a bounding rectangle for every character of a text range. The display model also exposes a bounding rectangle for every character and calculates a point from that rectangle. I'm pretty sure that IAccessible2 implements per character bounding rectangles as well.
Therefore, I propose an additional boundingRectangle property on textInfo objects that calculates the bounding rectangle of the current text range. This should be pretty easy when we use locationHelper (#7537). This will also allow us to implement de pointAtStart property for UIATextInfo, in which case moving the mouse to the current review position should be much more accurate. It would also allow detailled tracking of the browse mode position in Microsoft Edge and Microsoft Word with UIA enabled, that is, if both of them implement this properly.
cc @michaelDCurran