SelectableDecoratorNode

[amyworrall]

SelectableDecoratorNode Summary:

Test Plan:

Reviewers:

Subscribers:

Tasks:

Tags:

[facebook-github-bot]

@amyworrall has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[amyworrall]

Continuing my work on NodeSelection, here we have an actual working use case.

This diff does a number of things:

• Made the various editing event handling methods on RangeSelection (e.g. deleteCharacter()) public as part of BaseSelection.
• Documented BaseSelection
• Fixed a logic bug in transferStartingElementPointToTextPoint()
• Implemented more of NodeSelection, supporting deleting and replacing nodes
• Further improvement of ResponderForNodeSelection, which is the thing that tracks keyboard input and events when the text view is not handling them. (Note, on iOS, if the TextView is handling events, then a caret or selection will be shown. To do something else, such as NodeSelection where we draw our own borders, we have to tell the TextView to stop handling events.)
• Created a new class SelectableDecoratorNode, which handles the boilerplate for allowing the decorator to respond to clicks.
• Created SelectableImageNode as an example for using this.

Future plans:

• Support styling the border for selected SelectableDecoratorNodes
• Support shift-tap multi-selection
• When node selection becomes empty, automatically revert back to range selection
• Further testing for edge cases when swapping between node and range selections, especially in cases where the swap is forced by incoming events.
• On iOS, tap (aka click) handling does not fire a Lexical event: it is handled directly e.g. in the SelectableDecoratorNode class, and there's no way of hooking in earlier than that. Consider making SelectableDecoratorNode fire the Lexical event and also listen to its own event, instead of handling the tap directly.