| Age | Commit message (Collapse) | Author |
|---|
|
|
|
See: https://github.com/philc/vimium/pull/715
|
|
|
|
|
|
|
|
|
|
When a chrome history entry is removed, remove that entry from our
history too. Same when the entire history is removed.
|
|
Highlight all matches in a vomnibar suggestion, not just the first.
|
|
Minor fixes.
|
|
|
|
With the previous version, a query like "hello there" yielded:
[ "hello", "", "", "there" ]
as the queryTerms.
|
|
This is looks wrong, and is inconsistent with the way the equivalent
calculation is handled elsewhere.
This commit fixes it.
|
|
1. Factor out `pushMatchingRanges`:
This then allows us to ...
2. Add unit tests for `pushMatchingRanges`
In effect, these tests verify where matches are highlighted in suggestions.
3. Added Utils.zip. This helps simplify `pushMatchingRanges` unit tests.
4. Improve comments.
|
|
|
|
This is a no-op, currently. It's just setting up the RegexpCache
interface for subsequent development.
|
|
Also initialize tabInfo fields at once, so as to avoid unnecessary
hidden class transitions.
|
|
|
|
Previously, we were throwing errors when trying to modify nonexistent
members of `openTabs`, due to messages arriving after the onRemoved
notification. We now delay garbage-collecting openTabs, and rename
openTabs to tabInfoMap to reflect that the tabs are not necessarily
open.
|
|
|
|
|
|
Improve consistency and fix bug in relevancy calculation.
|
|
Additionally, add relevant test cases.
|
|
|
|
Problem:
- The word relevancy calculation is case sensitive, all other matching
is case insensitive.
Improve consistency:
- Highlighting of elements in the vomnibox is case insensitive; this
does not match the case sensitive relevancy calculation.
Fix:
- Bookmark titles, in particular, tend to contain capital letters.
Unless the query term also contains the relevant capital letters,
then the term was scored at zero, pushing what seem to be good
matches to the bottom of the list. In fact, they were only included
in the list at all because they happen to pass the
`RankingUtils.matches()` test.
|
|
Changes:
- use natural order for bookmark traversal
- eliminate use of O(N^2) `shift`
|
|
Also correct a bug with the show / hide advanced commands button.
|
|
|
|
This avoids the need to continually re-parse the strings each time we
load the option value.
|
|
|
|
Closes #380.
|
|
|
|
Closes #671.
|
|
This interacts with these lines from settings.coffee:
don't store the value if it is equal to the default, so we can change the defaults in the future
if (value == @defaults[key])
@clear(key)
If the default value is numeric, then this test NEVER succeeds (because
"==" is compiled to "===", and the types don't match).
So, scrollStepSize is stored in localStorage even if it has its default
value. Which obviates the intention of the line quoted above.
|
|
For some reason addCssToPage seemed to break on Chrome 24.
Closes #676.
|
|
- https://github.com/philc/vimium/pull/682.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
'background-color' is no longer sufficient to override our default
styling. Refs #626.
|
|
|
|
|
|
Errors were detected using coffeelint.
|
|
|
|
The help dialog now gets showAdvancedCommands directly from settings.
|
|
Convert them to Coffeescript at the same time.
We really need to set up some automated way of running these tests, to
ensure they don't keep breaking.
|
|
|
