Hi, Pete. The reason is to save an extra call. From my understanding
AT wants to know the caret offset within deepest accessible having a
caret. This doesn't add complexity to server implementation (as you
said all it's needed is to query text interface and call caretOffset).
We could introduce mag
If you both think that new method is overkill then I'm fine to go with
relations approach. However this relation makes sense on document
accessible only and it'd be nice to introduce new method to obtain it,
otherwise AT needs to crawl hierarchy.
Next IA2 spec is going to provide a method to get e
