Hello everyone, One of the Chrome feature I miss the most is MRU tab navigation. This was already discussed and as the issue http://code.google.com/p/chromium/issues/detail?id=5569 was marked as "WontFix", I thought it would be great to do an extension to implement the MRU tab navigation. First I looked into how keyboard events could be handled so I could intercept the CTRL+TAB key strokes. I found out that I should use content scripts, hook to onkeydown and onkeyup events, cancel the default behavior by setting returnValue of the event to false. Everything worked perfect so I even released the extension on the web for others to test it. Today, big surprise, I have updated Chrome to 4.0.223.11 only to find out that my extension is no longer working. Of course, I started a debugging session and found that browser's shortcuts (like CTRL+TAB) no longer can be overridden using the onkeydown event, actually the event is not even fired for that combination anymore. I thought "hey, maybe I was so unfortunate that I worked on a Chrome version - 4.0.206.1 - that was just broken enough to make my extension work", so I looked into the issue database and found issue http://code.google.com/p/chromium/issues/detail?id=1394 which actually is very related to my problem, CTRL-TAB interception by some pages can make tab navigation via CTRL-TAB impossible. Funny enough the issue is marked also as "WontFix" because "The page should always get a first crack at the keyboard events, so there is not much to be done here.". If this would have been respected, I wouldn't have any problems.
Some questions: 1. The current behavior of not passing CTRL-TAB to pages (content scripts) is actually an issue in the current version or this would be the normal behavior from now on ? 2. Is there any other way to intercept the CTRL-TAB ? 3. Considering that the Chrome developers change very often the extensions API and behavior, how does someone expects to have Chrome extensions developed, since you can't tell if it will work on next release ? 4. Is there any roadmap we could see somewhere/anywhere for the extensions API development ? 5. Which are the "safe" API/behavior to use when developing an extension, so we don't have to worry it will not work the next day? Thank you, Puiu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
