aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2015-06-01Merge branch 'unified-settings-implementation'Stephen Blott
2015-06-01Always call performPostUpdateHook after Setting updates (.set/.clear)mrmr1993
2015-06-01Simplify searchEngines default value.Stephen Blott
2015-06-01Note bug in settings.Stephen Blott
(This bug has been around for quite some time. I just noticed it now.)
2015-06-01Fix error reading settings from chrome.storage.sync.Stephen Blott
2015-06-01Eliminate possibility of race condition.Stephen Blott
See newly-added long comment for details.
2015-06-01Refactor and eliminate Sync object.Stephen Blott
2015-06-01Only propagate changes from chrome.storage.sync.Stephen Blott
2015-06-01Remove LinkHints.init()...Stephen Blott
LinkHints.init() isn't doing anything.
2015-06-01Re-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-31Add a default value for helpDialog_showAdvancedCommandsmrmr1993
We need this because Settings rejects key/value pairs from chrome.storage for which there were no default values. Previously, this only meant that the setting would not sync; now it meant that the setting wasn't ever made available to the frontend. This commit fixes it, and now the setting will sync.
2015-05-31Remove code supporting the former settings port from the frontendmrmr1993
2015-05-31Update the comment by the settings object in the frontendmrmr1993
2015-05-31Remove all remaining references to frontend settingsmrmr1993
2015-05-31Init Settings directly instead of via settings.load, and only do it oncemrmr1993
2015-05-31Replace settings.addEventListener with Settings.addEventListener in the frontendmrmr1993
2015-05-31Replace settings.set with Settings.set in the frontendmrmr1993
2015-05-31Replace settings.get with Settings.get in the frontendmrmr1993
2015-05-31Rewrite settings as a tight wrapper around Settings, tweaks for testsmrmr1993
2015-05-31Add event listeners to settings, support load eventsmrmr1993
2015-05-31Add Settings.isLoaded to the unified settings implementationmrmr1993
2015-05-31Fix 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-31Fully remove unused option.Stephen Blott
(This was supposed to have been removed previously. Oops!).
2015-05-31Tweak Google Maps URL.Stephen Blott
Conflicts: misc/completion_engines/completion_engines.md
2015-05-31Fix completion engine regular expressions.Stephen Blott
We need to use "\\." to get a literal ".".
2015-05-31Tweak the release notes for as-yet unreleased features.Stephen Blott
2015-05-31Merge pull request #1486 from smblott-github/advanced-options-buttonStephen Blott
Move "show-advanced-options" to a fixed-position button.
2015-05-31Merge pull request #1675 from smblott-github/map-space-keyStephen Blott
Allowing mapping <space>.
2015-05-31Merge pull request #1700 from smblott-github/help-page-vomnibar-commandsStephen Blott
Move Vomnibar commands to own category on help page.
2015-05-31Merge pull request #1697 from smblott-github/vomnibar-map-with-prepopulated-textStephen Blott
Direct keyboard access to custom-search engines via keyword flag
2015-05-31Merge pull request #1699 from smblott-github/add-link-to-wiki-to-help-pageStephen Blott
Add a link to the wiki on the help page.
2015-05-31Tweak release notes.Stephen Blott
2015-05-30Merge pull request #1702 from smblott-github/completion-for-google-mapsStephen Blott
Completion for google maps
2015-05-30Search completion; refactor regexp parsing (simplification).Stephen Blott
2015-05-30Search completion; simplify completion-engine definitions.Stephen Blott
2015-05-30Search completion; remove unused code.Stephen Blott
This removes a couple of lines which should have been removed previously.
2015-05-30Search completion; add support for Google Maps completion.Stephen Blott
2015-05-30Move Vomnibar commands to own category on help page.Stephen Blott
The help page gets pretty lopsided when advanced commands are shown. This balances things out a bit by creating a new category for Vomnibar commands in the right-hand column.
2015-05-30When 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-30Document visual-mode commands in README.Stephen Blott
2015-05-30Add a link to the wiki to the help page.Stephen Blott
Ass suggested in by @LarryBattle in #1643.
2015-05-30Use 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.
2015-05-29Verify keyword for custom search-engine activation.Stephen Blott
For ... map s Vomnibar.activate keyword=g ... we verify that "g" is indeed a custom search-engine keyword before setting it. If it is not, we output a console.log message and launch a vanilla vomnibar. (An alternative would be to bail.)
2015-05-29Move search-engine parsing to Utils.Stephen Blott
This will allow us to use the same search-engine parsing code in the background page and in content scripts.
2015-05-29Prepopulate @customSearchMode in vomnibar.Stephen Blott
This avoids a flicker whereby the keyword is first inserted into the input, then removed.
2015-05-29Merge pull request #1599 from mrmr1993/settings-refactorStephen Blott
Separate Settings from the background page, and use it directly in options.html/popup.html
2015-05-29Make a check more coffeescript-ymrmr1993
2015-05-29Disable Tween on XML pagesmrmr1993
2015-05-29Also disable all externally-used functions for XML.Stephen Blott
2015-05-29Disable UIComponent for XML documentsmrmr1993
If the page is an XML document, nothing we do works: * <style> elements show their contents inline, * <iframe> elements don't load any content, * document.createElement generates elements that - have Element.style == null, and - ignore CSS. This commit stops us from injecting anything into the DOM from UIComponent, fixing #1640.