Comment #34 on issue 13891 by lost.goblin: Keypress event not fired for some Ctrl+key combinations, doesn't match WebKit or Chrome 1. http://code.google.com/p/chromium/issues/detail?id=13891
Yes, I understood that. I should have been more clear: will I be able to stop propagation and prevent the default behavior from taking place? Part of the whole point of the extension is to keep Ctrl-W from closing the window. I'm currently using the keydown events, and stopping the propagation of those seems to do the trick, but just wanted to make sure I understood this right (even after writing the extension I still feel rather clueless about how JavaScript keyboard events really work). BTW, in case anyone is interested in checking it out: http://repo.cat-v.org/burning_chrome/hosaka/ Thanks again and sorry if I'm being excessively obtuse :) -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
