For a while, |is_browser_shortcut| in WebKeyboardEvent was broken ( bug 721384 ). It was always false.

That is now fixed due to a revert of some code that seemed correct and passed review. But that's rather scary, as |is_browser_shortcut| is used in input handling for correct processing of events, and I'm adding even more code that depends on it (bug 709765).

I'm going to try to get a working test for it, to make sure it doesn't regress again, but I may have to punt and give this to the input event owners.