| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2015-06-10 | Make all find mode updates go via the HUD in preparation to use an input | mrmr1993 | |
| 2015-06-10 | Decide find mode text in the HUD iframe, not in frontend | mrmr1993 | |
| 2015-06-10 | Merge branch 'link-hints-keypress' (#1722). | Stephen Blott | |
| 2015-06-10 | Remove legacy (broken and unnecessary) calls. | Stephen Blott | |
| 2015-06-10 | Simplify activate-on-enter logic. | Stephen Blott | |
| 2015-06-09 | Minor touch ups. | Stephen Blott | |
| 2015-06-09 | Make LinkHints a class (LinkHintsMode). | Stephen Blott | |
| Functionality wise, this is a no-op. However, since we now create a new LinkHintsMode object on every "f", we don't need to be so careful about resetting the state on exit. | |||
| 2015-06-09 | Use tab to select filetered link hints. | Stephen Blott | |
| 2015-06-09 | Tweak comments re. keydown versus keypress. | Stephen Blott | |
| 2015-06-09 | Only look up linkHintNumbers once. | Stephen Blott | |
| 2015-06-09 | Alphabet hints, use keydown for defaults. | Stephen Blott | |
| See #1722. When Settings.get("linkHintCharacters") is its default value, this preserves the legacy behaviour of using the keyChar from keydown events for link-hint matching. This admits users using either Latin or non-Latin characters for link hints. | |||
| 2015-06-08 | Remove "experimental" comment. | Stephen Blott | |
| I think we can safely remove this comment now, @mrmr1993. This is working out very nicely. | |||
| 2015-06-08 | Make hint filters classes. | Stephen Blott | |
| 2015-06-08 | Refactor to keydown, as required. | Stephen Blott | |
| 2015-06-07 | Exit link-hint mode on click or scroll. | Stephen Blott | |
| Exit on click because, if the user is clicking stuff, then they're probably no longer interested in selecting links. Exit on scroll because, if the user is scrolling, then the link hints can all go out of the viewport. | |||
| 2015-06-05 | Global marks; always treat ` and ' as local marks. | Stephen Blott | |
| On some keyboards (who knows?) "`" or "'" could be shift keys. In this case, with the previous implementation, these would be treated as global marks and `` would be unusable. This commit fixes that problem. | |||
| 2015-06-05 | Global marks; global marks are always recorded for the top frame only. | Stephen Blott | |
| With global marks, we may later create a new tab when the mark is used. When doing so, we should always be using the URL and scroll position of the top frame within the tab. For example, if a global mark is created from within the Hangouts frame of Google's Inbox and the mark is later used, then we should create a new tab for Inbox's URL and scroll position, not for the Hangout's URL and scroll position. | |||
| 2015-06-05 | Global marks; fix indentation. | Stephen Blott | |
| 2015-06-05 | Use keypress (instead of keydown) for link hint characters. | Stephen Blott | |
| This should make link hints usable on non-Latin keyboards (e.g. Russian keyboards). Fixes #1387. (Maybe - because it's not clear from the discussion there exactly what users want.) | |||
| 2015-06-05 | Fix event suppression for Marks keyboard events. | Stephen Blott | |
| 2015-06-04 | Unwind passing key and registry entry for marks. | Stephen Blott | |
| As suggested by @mrmr1993 in #1716. | |||
| 2015-06-04 | Use only ' and ` for jumping to previous position. | Stephen Blott | |
| As suggested by @mrmr1993 in #1716. | |||
| 2015-06-04 | Global marks; only handle messages in main frame. | Stephen Blott | |
| On sites with several frames (e.g. Facebook), if we allow all of the frames to handle the setScrollPosition and showHudForDuration messages, then the focus ends up in an arbitrary frame. And, on Facebook, say, Vimium ends up broken until the focus is returned to the main frame. So, we only handle these messages in the main frame. | |||
| 2015-06-04 | Global marks; focus and only scroll in the main frame. | Stephen Blott | |
| 2015-06-04 | Exit marks modes on escape. | Stephen Blott | |
| 2015-06-03 | Modes, better comments. | Stephen Blott | |
| 2015-06-03 | Add mark commands to README, more simple refactoring. | Stephen Blott | |
| 2015-06-03 | Add mark commands to README, simple refactoring. | Stephen Blott | |
| 2015-06-03 | Refactor (to setPreviousPosition) to clarify Marks logic. | Stephen Blott | |
| 2015-06-03 | Also set previous position for before global mark movement. | Stephen Blott | |
| 2015-06-03 | Re-implement Marks, incl `` binding. | Stephen Blott | |
| 2015-06-03 | Fix tests for #1713... | Stephen Blott | |
| ... which is weird, because the tests are passing here. Let's see what Travis makes of this. | |||
| 2015-06-03 | Refactor to avoid having to cover all keyboard event cases. | Stephen Blott | |
| It's pretty common that we want to suppress all keyboard events, so let's support that in modes.coffee, thereby simplifying handlers elsewhere. | |||
| 2015-06-03 | Fix marks (incl. global marks)... | Stephen Blott | |
| Fixes #1712: - Make global marks work. - Add mode indicator. - Don't fail for global marks on background page if mark is not set. - Give HUD warning for global marks if global mark is not set. (The diff is big but, which the exception of infrastructure refactoring, the main change is to not exit on <Shift>, thereby fixing #1712). | |||
| 2015-06-01 | Merge branch 'unified-settings-implementation' | Stephen Blott | |
| 2015-06-01 | Remove LinkHints.init()... | Stephen Blott | |
| LinkHints.init() isn't doing anything. | |||
| 2015-06-01 | Re-work unified settings. | Stephen Blott | |
| This is a minor re-working of #1705 from @mrmr1993. The main changes are: - Simplify initialisation logic. - Always initialise Settings immediately and automatically (ie. don't initialise Settings separately and manually in the background, content scripts, options and tests). - Get rid of addEventListener (it's only being used for on "load"). - Add Settings.use() in its place. | |||
| 2015-05-31 | Update the comment by the settings object in the frontend | mrmr1993 | |
| 2015-05-31 | Remove all remaining references to frontend settings | mrmr1993 | |
| 2015-05-31 | Init Settings directly instead of via settings.load, and only do it once | mrmr1993 | |
| 2015-05-31 | Replace settings.addEventListener with Settings.addEventListener in the frontend | mrmr1993 | |
| 2015-05-31 | Replace settings.set with Settings.set in the frontend | mrmr1993 | |
| 2015-05-31 | Replace settings.get with Settings.get in the frontend | mrmr1993 | |
| 2015-05-31 | Rewrite settings as a tight wrapper around Settings, tweaks for tests | mrmr1993 | |
| 2015-05-31 | Fix options page error. | Stephen Blott | |
| "setIcon" should be in the list of messages delivered to the options page (and for which there is no handler). | |||
| 2015-05-31 | Merge pull request #1697 from smblott-github/vomnibar-map-with-prepopulated-text | Stephen Blott | |
| Direct keyboard access to custom-search engines via keyword flag | |||
| 2015-05-31 | Merge pull request #1699 from smblott-github/add-link-to-wiki-to-help-page | Stephen Blott | |
| Add a link to the wiki on the help page. | |||
| 2015-05-30 | When showing the help dialog, simulate-click it. | Stephen Blott | |
| On smaller screens (and with the advanced options unfolded), the help page can need scrolling. Currently, you have to click it to give it the focus. Here, we simulate-click it, so that "j" and "k" scrolling is active immediately. | |||
| 2015-05-30 | Add a link to the wiki to the help page. | Stephen Blott | |
| Ass suggested in by @LarryBattle in #1643. | |||
| 2015-05-30 | Use the term "options" instead of "flags" for command options. | Stephen Blott | |
| "Flags" implies binary toggles. The term "options" seems more consistent with what's actually going on here. | |||
 |
index : vimium | |
| The hacker's browser. |
| aboutsummaryrefslogtreecommitdiffstats |
path: root/content_scripts