vimium/tests/dom_tests, branch 1.49 The hacker's browser. Force our key event handlers to have the highest possible priority 2014-11-02T05:39:07+00:00 mrmr1993 2014-11-02T05:39:07+00:00 dafa166364ff9a30b0cc2f0d160fcbcfc01cc61e * 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)). 
* 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)).
Merge pull request #922 from camflint/FixBuildAndTestTasksOnWindows 2014-08-12T15:28:42+00:00 Phil Crosby 2014-08-12T15:28:42+00:00 be76291cfdbae4ce142efe2ab35795fff91e12e6 Fix build and test tasks on Windows 
Fix build and test tasks on Windows
 Add a TODO to tighten up the contract of some tests 2014-08-12T15:22:33+00:00 Phil Crosby 2014-08-12T15:21:16+00:00 4ab75878b3d59c0f970195bfae191781e0b9f5b3 






Match mixed-case relationship links in goNext/goPrevious
2014-08-05T07:14:30+00:00

Vincent Bernat

2014-08-05T07:11:37+00:00

17d7b88ee05ee940404fef5bb605c9b7665b15b8

Link types are case-insensitive:
 http://www.w3.org/TR/html5/links.html#linkTypes

This should fix #1115.





Link types are case-insensitive:
 http://www.w3.org/TR/html5/links.html#linkTypes

This should fix #1115.







Add a test for "link rel='next'" kind of link.
2014-08-05T07:10:01+00:00

Vincent Bernat

2014-08-05T07:05:11+00:00

c27961a1700cdbcbf90d53420b1df304988d6c5d

While this is not strictly valid, we don't put the link markup into
`<head>` to avoid adding more code just for those two new tests.





While this is not strictly valid, we don't put the link markup into
`<head>` to avoid adding more code just for those two new tests.







Fix build and test on Windows.
2014-06-08T20:38:02+00:00

spccdt

2013-09-21T18:40:29+00:00

06729270f7e3968d9a6bd6c8ec8d47f3afe97bd7












Fixed detection of links which are only partially inside the viewport
2013-10-28T20:13:37+00:00

Stanley Shyiko

2013-10-28T20:13:37+00:00

88cbe89247a4ebdf9498d77eb0f7e675b7a4c785












Changed deprecated chrome.extension on chrome.runtime in all files and fix tests
2013-09-12T11:26:50+00:00

Maksim Ryzhikov

2013-09-12T11:26:50+00:00

9278d262c56301e997ccb214814543f64c7ba30b












Add runtime.getManifest() stub to Chrome mock
2013-05-08T21:34:30+00:00

sainaen

2013-05-08T21:34:30+00:00

453d35f24b77fc92c7aaf61f625878ea9848e9c6












Add onMessage() stub to Chrome extension API mock
2013-05-06T19:43:22+00:00

sainaen

2013-05-06T19:17:25+00:00

81567c3ce1eee182f63dbdf08647e9a111887b43