Additional bindings on `Input` would be beneficial

I’m thinking of these:

Binding('ctrl+left', 'word_left', 'previous word', show=False),
Binding('ctrl+right', 'word_right', 'next word', show=False),
Binding('ctrl+u', 'delete_left_all', 'delete left all', show=False),
Binding('ctrl+w', 'delete_left_word', 'delete left word', show=False),
Binding('ctrl+f', 'delete_right_word', 'delete right word', show=False),
Binding('ctrl+k', 'delete_right_all', 'delete right all', show=False)

and have already implemented the above in a subclass in an app I’m working on, seem to work reasonably. I could work up a PR but I’m not sure how the unit and integration testing for this kind of thing would work.

[willmcgugan]

I think that may be fixed in main. We were responding to key events for home and end, but these were replaced with bindings. So if the focused widget has a binding it will now prevent the parent from handling it.

[learnbyexample]

I’m not sure where the other functionality is implemented. Home/End are used to scroll the screen to top/bottom. What I’m asking is that when focus is in Input, it should not scroll the screen.