Bug 47803
| Summary: | [Meta] Portable part of TextInputController API should be owned by LayoutTestController | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Hajime Morrita <morrita> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Hajime Morrita
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
The original idea was that TextInputController implements AppKit NSTextInput protocol. I'm not sure where hasSpellingMarker came from.
Hajime Morrita
(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.