Plan: Handling Text Selection/Deletion

[trueadm]

This is an umbrella issue to cover all the various use-cases for keyboard text selection and text deletion.

Note: we may change parts of this plan.

Keyboard Text Selection

Moving backward/forward

• We should listen to left and right arrow events (without the relevant modifier for the OS)
• We may have to apply some polyfills around moving selection between blocks
• We may need to apply some custom logic around segmented/immutable nodes for accessibility purposes
• Otherwise, should use the default native browser behavior

Deleting backward/forward

• If beforeinput is supported we should attempt to use the boundary from getTargetRanges()
• If beforeinput is not supported, we should apply a naive (and cheap) boundary implementation
• We may need to apply some custom logic around the deletion of adjacent segmented/immutable nodes

Moving/Deleting a word backward/forward

• If Intl.Segmenter is supported, we should always use this to work out the right word boundary
• If Intl.Segmenter is not supported, we should check if native beforeinput is supported.
• If beforeinput is supported we should attempt to use the boundary from getTargetRanges()
• If beforeinput is not supported, we should apply a naive (and cheap) word boundary implementation

Moving/Deleting a line backward/forward

• If beforeinput is supported we should attempt to use the line boundary from getTargetRanges()
• If beforeinput is not supported, we should apply a naive approach and move the selection to the start of the current block.

Moving a block backward/forward

• Should use the default native browser behavior