What level of simulation should be in Keyboard interactor?

For the this moment Keyboard interactor allows to type some characters and simulates keyDown and keyUp events for the most possible keys. But there might be different scenarios where Keyboard interactor doesn't work well or doesn't support at all. For example:

• Using functional keys, like Home/End/Arrows to move the cursor in a text field to later insert some text. Should Keyboard interactor be responsible for the selectionRage or not?
• Using Enter for submitting a form if it is on a page.
• Removing characters from a field by using Backspace/Delete keys.
• Using PageUp/Down for the scrolling a page.
• Supporting case with testing clipboard logic, like user selects a part of the text on page, hits Ctrl+C and then pastes it somewhere. Should it be specific Clipboard interactor for it?
• Changing the focus by the Tab.

I mean all cases that supported by a browser in the native way, when you don't need a specific onKeyDown handler.

Start by reviewing the Keyboard interactor and its current keyDown, keyUp, and character-typing behavior. Compare the listed native browser cases, including selection, form submission, deletion, scrolling, clipboard use, and focus changes, then define the supported scope and whether clipboard behavior belongs in a separate interactor.