| Age | Commit message (Collapse) | Author | 
|---|
|  | into mrmr1993-add-html5-input-types | 
|  |  | 
|  |  | 
|  | This fixes the tests, which were broken by makeXPath trying to recurse
over Arrays with an augmented prototype. | 
|  | This is designed to address several issues:
* `<input type="range" />` elements don't respond well to the simulated
click; they always reset their value to the minimum.
* The lack of `mouseup` event from the simulated click makes
`<input type="range />` elements slide when the mouse is moved.
* HTML5 adds a large number of text-based `<input>`s that should be focused
like the `type="text"` case, for consistency. (Using a blacklist halves
the number of types we have to list.)
* An `<input>` with a `type` the browser doesn't support is rendered as
a `type="text"`, so a blacklist ensures that the focusing action is
consistent on all elements behaving as `type="text"`. | 
|  |  | 
|  | * The `window` object receives key events before the `document` object,
and so any event listeners on `window` get priority. This commit
switches from binding `keydown`, `keypress`, `keyup` on `document` to
on `window`.
* We were using `event.stopPropagation()` to prevent other event
listeners from firing if we had handled an event. This stopped the event
from propagating to other elements/objects and triggering their event
listeners, but didn't block event listeners registered on the same
object as ours. Switching to `event.stopImmediatePropagation()` ensures
that our event listener is the last to run for the event.
Fixing these issues allows Vimium to regain control over key events in
Google Groups (eg. the [vimium-dev
group](https://groups.google.com/forum/vimium-dev)). | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | For some reason addCssToPage seemed to break on Chrome 24.
Closes #676. | 
|  | Previously, handlerStack was designed only for removal of the handler
right at the top of the stack. However, some handlers sought to remove
themselves when they were not at the top of the stack, creating
confusion. The new handlerStack ensures that such removal can always be
done safely. | 
|  |  | 
|  | Errors were detected using coffeelint. | 
|  |  | 
|  | * vimium_frontend now has a pretty decent set of exports
* Generic linkHints code has been moved to DomUtils, so future features
  can reuse the code. | 
|  |  | 
|  | This paves the way for the hints code to be reused in other modes. | 
|  |  |