vimium/background_scripts, branch 1.50

Simplify front-end settings logic.

2015-04-25T15:11:01+00:00

- Simplify the settings logic.
- Send a single request for all required settings (instead of 12
  inidividual requests for the 12 settings values we need in the front
  end).

Remove unused code.

2015-04-25T13:38:53+00:00

Track tab URL even if frame's URL changes.

2015-04-25T12:11:21+00:00

We track the URL of the active frame in each tab so that we can
correctly populate the rules in the page popup.

Previously, we tracked URL changes only on focus events.  This commit
moves that to isEnabledForURL, which is also called when the URL changes
as a result of web navigation.

Remove requirement for Chrome 41.

2015-04-25T09:12:42+00:00

Merge branch 'exclusion-rules-pushState-and-hash' of https://github.com/mrmr1993/vimium into mrmr1993-exclusion-rules-pushState-and-hash

2015-04-25T08:45:55+00:00

Conflicts:
	content_scripts/vimium_frontend.coffee

Merge remote-tracking branch 'origin/focus-main-frame' into focus-main-frame-merge

2015-04-25T06:50:31+00:00

Conflicts:
	content_scripts/vimium_frontend.coffee

Also rework to remove dependency on Chrome 41+ sendMessage API
(specifically, relating to optional target frameId argument).

Activate vomnibar in window.top; do not register framesets.

2015-04-25T06:23:41+00:00

When the vomnibar closes, it focuses its enclosing window.  If that is a
frameset, then we do not want to inadvertently register it.

Merge branch 'vomnibar-in-main-window' into vomnibar-in-main-window-merge

2015-04-25T06:06:31+00:00

Conflicts:
	background_scripts/main.coffee
	content_scripts/vimium_frontend.coffee

Re-check enabled state after history.pushState/location.hash is changed

2015-04-24T13:39:40+00:00

This uses the chrome.webRequest API to detect changes to page URL which
*do not* cause the content script to refresh.

Get incognto state directly from chrome.extensions.inIncognitoContext

2015-04-24T13:08:54+00:00