Open aartaka opened 1 year ago
Do you have other use cases beside the inspector?
Ideally, we would differentiate the input based on the "view" that's focused, that is, if it's the web view or the inspector. But it's not very clear to me how WebKit handles this.
Do you have other use cases beside the inspector?
One day, we might have inputs in the manual. And that would break them severely.
Ideally, we would differentiate the input based on the "view" that's focused, that is, if it's the web view or the inspector. But it's not very clear to me how WebKit handles this.
It doesn't, really :(
Maybe GTK can help us here to distinguish the windows...
Is your feature request related to a problem? Please describe. We have our
help-mode
with convenient navigation bindings. But I often end up opening an inspector or some other input side-by-side with our help pages, and then inputting text into these ends up invoking thehelp-mode
commands, because these are a single-key bindings. Not cool.Describe the solution you'd like Let's only enable these bindings for CUA scheme, because:
Removing
help-mode
is useful, it is really (pun intended) helpful, after all. So let's just lessen the damage to Emacs/VI people :)