Derived from Bug 47659. Following set of TextInputController API is not IM framework specific and should be available via LayoutController. - textInputController.attributedSubstringFromRange - textInputController.firstRectForCharacterRange - textInputController.selectedRange - textInputController.hasSpellingMarker
The original idea was that TextInputController implements AppKit NSTextInput protocol. I'm not sure where hasSpellingMarker came from.
(In reply to comment #1) > The original idea was that TextInputController implements AppKit NSTextInput protocol. I'm not sure where hasSpellingMarker came from. Sure! So I keep NSTxtInput originated method, and will add aliases or introduce test-specific APIs to DRT. The goal of this change is to make IM-independent editing tests portable.