I’ve noticed that web browsers have been good at capturing Ctrl+<char> sequences and passing them on to the right context.
For example, if I have a terminal console open in a web browser (e.g. google code, or jupyter notebook), I notice that using Ctrl+C to kill a process does correctly pass through my desktop manager, through my web-browser, and to the console to kill the process. If I click just outside of the console window but still within the web-browser, then Ctrl-C acts like a normal copy command.
Not sure what my point is, other than it perpetually boggles my mind how many layers of software a key stroke has to pass through before it acts on the actual layer that you want.
I’ve noticed that web browsers have been good at capturing
Ctrl+<char>sequences and passing them on to the right context.For example, if I have a terminal console open in a web browser (e.g. google code, or jupyter notebook), I notice that using Ctrl+C to kill a process does correctly pass through my desktop manager, through my web-browser, and to the console to kill the process. If I click just outside of the console window but still within the web-browser, then Ctrl-C acts like a normal copy command.
Not sure what my point is, other than it perpetually boggles my mind how many layers of software a key stroke has to pass through before it acts on the actual layer that you want.