| Age | Commit message (Collapse) | Author |
|
|
|
valid command given the current key queue.
|
|
|
|
|
|
issue #32.
|
|
from the settings page.
|
|
|
|
|
|
|
|
|
|
the real search.
|
|
|
|
page until you hit enter and use 'n' or 'N'. While you type the first matching result will stick. Closes #24.
|
|
bit funny.
|
|
Lifehacker.com's right bar would previously cover our HUD.
|
|
|
|
|
|
Closes #25.
|
|
|
|
and out.
|
|
determine if it's visible.
I previously switched the logic to use the center of the bounding box, but that does
not work well for multi-line links.
|
|
link hints.
|
|
|
|
|
|
Fix involved two things: (1) unblocking the display of real spaces in the HUD when mixed in with the fake spaces intentionally inserted, (2) fixing our keydown handler to understand the scenario when we need to use the unicode keyIdentifier.
|
|
level style sheets. Fixes #22.
|
|
|
|
gets zoomed.
|
|
|
|
|
|
the feedback timeout.
|
|
hints. Fixes #19.
|
|
detect if its visible.
This is a slightly more accurate heuristic and fixes #17.
|
|
number to a base-n string. Fixes #21.
|
|
few links
|
|
|
|
Also, if the second key is itself a valid first key or a standalone command, keep it or execute it accordingly. Closes #20.
|
|
|
|
|
|
detection throws javascript error.
|
|
|
|
|
|
|
|
be executing
in the background.
This will be the case if you open a new tab via middle-clicking on a link.
|
|
(google search results) and <img>
|
|
|
|
|
|
feature (maybe).
|
|
|
|
(google search results) and <img>
|