aboutsummaryrefslogtreecommitdiffstats
path: root/background_page.html
AgeCommit message (Collapse)Author
2010-09-23A bunch of changes having to do with the frame support patch:Ilya Sukhar
- Focus the largest frame by default - Change the border styling to match link hints - Clean up framesForTab when tab is closed - Don't cycle through parent. This may break some sites. Needs more testing. - Fixed some naming and style - Added seven1m to CREDITS - Updated README
2010-09-10Make 'gi' compatible with repetition, i.e. 5gi will focus the fifth input ↵ilya
box on the page.
2010-09-03Command to go to next frame.Tim Morgan
I remapped toggleViewSource to 'gs' and set 'gf' to nextFrame. Sorry this is such a huge commit. This is really the simplest way I can find to allow the extension to track all available frames as well as the currently-focused frame. If Chrome would allow access to window.frames[i], then this could probably be simpler.
2010-09-03Only show the Help Dialog on the focused frame.Tim Morgan
2010-09-03Fix view source toggle when inside a frame.Tim Morgan
2010-09-03Basic Support for FramesTim Morgan
Only the focused frame will act on key commands. On some sites (such as Gmail), the main frame is already focused, so commands just work. For other sites, focusing the desired frame may be necessary, which can be done with the Tab key (not optimal) or by clicking with the mouse (even less optimal). An additional command to cycle through frames is desirable, which will likely come in a future commit.
2010-06-29remove spammy console.log i committed by accidentilya
2010-06-27Don't self close a script tag on the background page. Fixes #169.Phil Crosby
2010-06-22add goUp to the readme command listing - this needs to be deprecated for ↵ilya
something auto generated
2010-06-01Document named key functions (per philc)Conrad Irwin
2010-06-01Allow mapping to arrow keys and f-keysConrad Irwin
Conflicts: commands.js
2010-05-18Add a link to the Options page in the vimium help dialog. Closes #87.Phil Crosby
2010-04-19Pull the version number from the manifest file instead of hard coding itPhil Crosby
2010-04-17Undo 'Keep tab queue indices updated when a tab is detached'.int3
It does not follow Chrome's native behavior (and was buggy anyway.)
2010-04-10Move some code into init() so that it's clear that it executes once and is ↵ilya
part of initialization.
2010-04-10whitespaceilya
2010-04-10Another fix for tab positioningint3
2010-04-10Keep tab queue indices updated when a tab is detachedint3
2010-04-10Indentationint3
2010-04-10Stylistic modifications and update of commentsint3
2010-04-10Apply saving of scroll positions to all tabs, no matter how they are closed.ilya
2010-04-10Maintain accurate tab indices while ignoring chrome://newtabint3
2010-04-10Ensure Restore Tab works immediately upon extension installunknown
2010-04-02Add more robust support for keeping track of positions/windows when tabs are ↵ilya
moved within or between windows.
2010-04-02whitespaceilya
2010-04-02Fix memory leak from tabQueueunknown
2010-03-31Don't put the new tab page into the tab restoration queue.ilya
2010-03-31Avoid creating a separate tabQueueEntry object when we can just reuse the ↵ilya
object used in openTabs.
2010-03-31Clean up naming/style in the previous commit and small bugs.ilya
2010-03-31Restore Tab now recreates the tab in its old position.unknown
Also, Restore Tab is now able to restore all tabs, no matter how they were closed (via vimium keys, with the mouse, or with native Chrome shortcuts).
2010-03-28Fix chaining of previousTab/nextTab commands. This closes #93.ilya
2010-03-24Small modification to Bill's fix.ilya
2010-03-24checking in a fix for issue 98, link highlight positioning bugBill Mill
2010-03-09Refresh completion keys on all tabs and associated data structures after key ↵ilya
mappings are saved.
2010-03-09Bump version numbers to 1.16 in preparation for release.ilya
2010-03-09Fix a bug where if you add a mapping, save, and then remove it -- it won't ↵ilya
get actually unmapped.
2010-03-09Some minor style changes.ilya
2010-03-09Add a dialog to show all available commands for key mappings under the ↵ilya
options page.
2010-03-07Display the current version in the help dialog. Hide link to homepage.Phil Crosby
2010-03-07Show a help dialog when pressing ? which displays all of the current ↵Phil Crosby
keybindings o_O
2010-03-07Fix a bunch of key handling related bugs in one swoop. ilya
We were incorrectly generating valid first keys and completion keys for <c-x> type commands. This closes issue #85 and the alt+d override issue.
2010-02-27Key Mapping - Don't try to parse key mappings unless there's actually ↵ilya
something saved.
2010-02-26Key Mapping - Initial support. Basics work.ilya
2010-02-26Key Mapping - Create an available commands structure and factor out the key ↵ilya
registry into commands.js
2010-01-31Add two more characters to the pool that link hints pulls from.Phil Crosby
This will let us highlight more links with strings of just 2 characters instead of needing to use 3. This is a good idea now that we are highlighting anything on the page with an onclick handler, which means more links will be highlighted across the board.
2010-01-30Add the link hint markers to the DOM all at once instead of piecemeal. This ↵Phil Crosby
avoids invaliding Chrome's getBoundingClientRect calls. This should sufficiently close #71.
2010-01-30Save the current version to localStorage, and when an update arrives, show a ↵Phil Crosby
user notification. This closes #64. Note that updates won't trigger until we've saved the user's version to their localStorage, which means this change will go into effect for our users the version *after* the next release (so 1.16).
2010-01-30Fix a reference error over the default settings in the background page.Phil Crosby
2010-01-22Move the link hints CSS to the background page, and create a setting for ↵Phil Crosby
user-definable CSS.
2010-01-18Merge branch 'master' of github.com:philc/vimiumPhil Crosby
Conflicts: settings.html