| Age | Commit message (Collapse) | Author |
|
We don't need to worry where frames are added, nextFrame will find the
right frame to start from anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Frameset frames have no content of their own -- they only embed other
pages in sub-frames. The user can't perform any actions (of ours or
the browsers) with a frameset focused, so we might as well just not
focus it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There are security issues with favicons as implemented previously. This
commit removes favicon support entirely.
|
|
github.com:mrmr1993/vimium into mrmr1993-smooth-scrolling-requestAnimationFrame
|
|
Tabs order; order tabs by recency for empty searches.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes refresh of state bug introduced in
046650ba22ac12ebb18d1eb109fe694016eb77c0.
|
|
This resolves #979.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
into mrmr1993-add-download-link-to-commands
|
|
|
|
|
|
mrmr1993-limitedRepeats
|
|
mrmr1993-fix-tab-restore
|
|
|
|
mrmr1993-fix-insertCSS-error
|
|
We were never using the area property, and it was causing an infinite
setTimeout loop on frames with height == 0 or width == 0 (often caused
by AdBlockPlus etc.).
|
|
|
|
This brings behaviour of the chrome.sessions codepath in line with the
legacy code.
|