Why do IAccessibleEditableText::cutText, copytext, and pasteText have
"position" parameters?
Why don't they just act on the current selection?
Or are they supposed to have a side effect of setting the current
selection, so that the client AT doesn't have to call IAText::setSelection
first? (If so, then this side effect does not seem to be documented
anywhere).
I see that AtkEditableText and AT-SPI also have "position" parameters for
cut/copy/paste of text, so IA2 probably did it "for historic reasons". But
what is the history, here?
I don't understand why these API's seem to be allowed to work outside of
the current selection, when any typical application always does
cut/copy/paste using the current selection.
Carolyn
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
