Status: Available
Owner: [email protected]
Labels: Type-Bug Pri-2 OS-All Area-BrowserUI

New issue 5496 by [email protected]: Tab and window management commands  
should not round-trip through the renderer
http://code.google.com/p/chromium/issues/detail?id=5496

Keyboard messages are sent to the current renderer for processing. This
allows the web page to override most keystrokes. If they are unhandled,
they are echoed back to the browser process.

This is good because web pages want to see the keystrokes. They can also
override interesting commands such as Ctrl-P for print (they may want to
provide their own print preview).

However, tab and window management commands aren't well suited for this.
Even if the web page doesn't override the commands (which is very rare and
possibly harmful or annoying to the user), the responsiveness of the
browser to these messages depends on the responsiveness of the current
renderer.

For example, if the current renderer is hung, Ctrl-W won't close the tab.
You have to use the mouse. If you have a slow or hung renderer and you use
Ctrl-PageDown to cycle through the tabs, it will stop on the hung one and
not continue.

I propose the following "non-maskable" commands which would be handled in
the browser and never sent to the web page for processing.

Ctrl-PageUp
Ctrl-PageDown
Ctrl-W
Ctrl-F4
Alt-F4 (this one probably already is)
Ctrl-T
Ctrl-N
Ctrl-Shift-N
Shift-Esc (task manager)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to