| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2015-05-27 | Merge pull request #1616 from mrmr1993/detect-inline-inline-fontSize-elements | Stephen Blott | |
| Fix for #1554. | |||
| 2015-05-27 | Consistent highlighting of search suggestions. | Stephen Blott | |
| Also suppress highlighting of matching text in previous suggestions. (It looks odd to have highlighting in some suggestions but not others, with no apparent difference to the user.) | |||
| 2015-05-27 | Fix significant typo. | Stephen Blott | |
| Fix incorrect property name from 764d70312f292882abe4940adf9fee3d6e834327. | |||
| 2015-05-27 | Merge pull request #1690 from smblott-github/do-not-deduplicate-tabs | Stephen Blott | |
| Two errors fixed... | |||
| 2015-05-27 | Tap-to-open only in omni-mode vomnibar. | Stephen Blott | |
| Do not use tab-to-open the vominibar in tabs mode. (It doesn't make any sense.) | |||
| 2015-05-27 | Merge pull request #1689 from smblott-github/direct-next-previous-tab | Stephen Blott | |
| Go directly to next/previous tab. | |||
| 2015-05-27 | Simplify index calculation. | Stephen Blott | |
| 2015-05-27 | Do not de-duplicate tabs vomnibar entries. | Stephen Blott | |
| 2015-05-27 | Go directly to next/previous tab. | Stephen Blott | |
| This makes nextTab and previousTab go directly to the relevant tab, without visiting intervening tabs -- all of which avoids a nasty flicker for 5J or 5K. | |||
| 2015-05-26 | Merge pull request #1685 from smblott-github/fix-ui_component-race-condition | Stephen Blott | |
| Fix UI-Component race condition on start up. | |||
| 2015-05-26 | Refactor to avoid potential race condition (cont). | Stephen Blott | |
| 2015-05-26 | Merge pull request #1686 from ↵ | Stephen Blott | |
| smblott-github/change-vomnibar-insert-text-indicator Change vomnibar insert-text indicator. | |||
| 2015-05-26 | Change vomnibar insert-text indicator. | Stephen Blott | |
| Use a rightwards hooked arrow instead of a small greater-than sign, which according to @philc, renders as a large greater-than sign on Macs, See #1651. | |||
| 2015-05-26 | Refactor to avoid potential race condition. | Stephen Blott | |
| I haven't seen this happen, but... It could be possible for the iframe's contents to load before this callback is called (on nextTick), in which case the "load" callback wouldn't be called. So we delay setting the iframe's source until nextTick has elapsed. | |||
| 2015-05-26 | Add comment noting why we need AsyncDataFetcher. | Stephen Blott | |
| 2015-05-26 | Merge pull request #1654 from smblott-github/options-page-use-header | Stephen Blott | |
| Add header for Advanced Options. | |||
| 2015-05-25 | Fix UI Component race condition on start up. | Stephen Blott | |
| Approach: Re-use the existing AsynDataFetcher class to "fetch" and use the iframe message port. Messages are queued until the iframe's contents have loaded and the message port is open. Fixes #1679. | |||
| 2015-05-21 | Search completion; must return an array from this filter. | Stephen Blott | |
| 2015-05-20 | Merge pull request #1674 from mrmr1993/only-escape-double-slashes-for-our-flags | Stephen Blott | |
| Only replace double-slashes in find mode if they precede our flags | |||
| 2015-05-20 | Only modify find mode regexps if it's a flag we want to match | mrmr1993 | |
| 2015-05-20 | Ensure that slashes are grouped in pairs in order for find mode queries | mrmr1993 | |
| This ensures that \\\r is interpreted as {escaped-\}{escaped-r} rather than \{escaped-\}r. | |||
| 2015-05-20 | Only replace double-slashes in find mode if they precede our flags | mrmr1993 | |
| This fixes #1673 | |||
| 2015-05-20 | Search completion; tweak appearance of historical search queries (descriptions). | Stephen Blott | |
| 2015-05-19 | Search completion; minor code review. | Stephen Blott | |
| 2015-05-19 | Add insertText visual indicator. | Stephen Blott | |
| Conflicts: background_scripts/completion.coffee | |||
| 2015-05-19 | Search completion; tweak appearance of historical search queries. | Stephen Blott | |
| 2015-05-18 | Fully fix 3646b8c999a9e4b864e8c529f84b64a3c2c74ff0. | Stephen Blott | |
| 2015-05-18 | Search completion; filter out the default search. | Stephen Blott | |
| See example in diff. Do not offer a suggestion if it is what the user would get anyway if they just hit <Enter>. | |||
| 2015-05-18 | Revert "Search completion; promote the top completion." | Stephen Blott | |
| This reverts commit 4309dcd3030687f3ed02b86bbdf7c485baaee4a5. This is a bad idea. It pushes the suggestion at the top of the list out of the way. Users aren't going to like that if it's the one they're looking for. Conflicts: background_scripts/completion.coffee | |||
| 2015-05-18 | Fix vomnibar stuck open. | Stephen Blott | |
| See #1671. The problem was that we were making the vomnibar visible in the frontend, even if the vomnibar initialisation was not yet complete, and the iframe port was not yet available. (Also, @activate() is never being called without options, so we can drop that test.) Fixes #1671. | |||
| 2015-05-18 | Merge pull request #1670 from ↵ | Stephen Blott | |
| smblott-github/retain-previous-matching-suggestions Retain previous matching completion suggestions. | |||
| 2015-05-18 | Search completion; retain previous suggestions (tweak highlighting). | Stephen Blott | |
| 2015-05-18 | Search completion; retain previous suggestions (comments and tweaks). | Stephen Blott | |
| 2015-05-18 | Search completion; retain previous (matching) suggestions. | Stephen Blott | |
| This address "UX Issue 2" from #1651. If the user types "w lake vict" and sees a suggestion "lake victoria perch", and continues "w lake vict pe", then we retain the previous suggestion (which still matches) despite the fact that the completion no longer delivers it. This creates a more consistent, Vimium-like vomnibar UX. | |||
| 2015-05-18 | Merge branch 'search-completion-UX-tweaks' | Stephen Blott | |
| 2015-05-18 | Merge branch 'vomnibar-insert-history-with-tab' | Stephen Blott | |
| Conflicts: background_scripts/completion.coffee | |||
| 2015-05-18 | Search completion; remove console.log(). | Stephen Blott | |
| 2015-05-18 | Search completion; promote the top completion. | Stephen Blott | |
| This puts the first (top) completion suggestion at the top of the list: either one or two <Tab>s away, depending upon whether a domain-completer suggestion is present or not. | |||
| 2015-05-18 | Search completion; do not adapt completion scoring. | Stephen Blott | |
| The relevancy score of completion suggestions should not change as the user continues to type. See "UX Issue 1" in #1651. (The effect of the previous implementation was that search completions would jump, unpredictably, up the suggestion list, often displacing suggestions from other completers for no reason which was apparent to the user.) | |||
| 2015-05-18 | Disable relevancy debugging (again). | Stephen Blott | |
| Oops. I left this on, again. | |||
| 2015-05-17 | use a less brittle approach to decoding URIs (fix tests). | Stephen Blott | |
| 2015-05-17 | use a less brittle approach to decoding URIs. | Stephen Blott | |
| 2015-05-17 | For shortened URLs, do not consider case. | Stephen Blott | |
| This ensures that URLs which differ only in their case are considered duplicates, hence one is dropped. | |||
| 2015-05-17 | TabToOpen: respect trailing options when extracting query terms. | Stephen Blott | |
| A custom search engine like this... i: https://www.google.ie/search?q=%s&num=30&newwindow=1&biw=1918&bih=1015&tbm=isch Google image search Should not match a URL like this... https://www.google.ie/search?q=bbc+sport | |||
| 2015-05-17 | TabToOpen: remove console.log. | Stephen Blott | |
| 2015-05-17 | TabToOpen: turn off relevancy debugging. | Stephen Blott | |
| 2015-05-17 | TabToOpen: more tidy up pre-PR (additional comments). | Stephen Blott | |
| 2015-05-17 | TabToOpen: more tidy up pre-PR. | Stephen Blott | |
| 2015-05-17 | TabToOpen: tidy up pre-PR. | Stephen Blott | |
| 2015-05-17 | TabToOpen: reactivate custom search engines. | Stephen Blott | |
| When the user begins editing the inserted text from a custom-search-engine suggestion, we reactivate the original custom-search-engine mode. | |||
