| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This reverts commit d00345f45b5b3e56970237799c69808527e91919.
This is not (and will not be) supported by Firefox.
|
|
This is one approach to fixing #2277 properly. (Currently there's a
temporary fix in place.)
This uses HTML5 imports in place of the content-script loader.
This is better than the current "fix" because content scripts are only
listed in one place two places (as opposed to six).
It's worse than the previous content-script loader, though, in that
content scripts must be listed in two places, instead of one.
Fixes #2277.
|
|
Follow on from 8601edd71e74ba522e32658309cb2e7acca8aeeb.
|
|
Scripts loaded via the content-script loader previously were loaded
synchronously. In recent versions of Chrome, they now seem to be loaded
asynchrnously, which causes errors.
This is a temporary commit to keep master healthy until I (or somebody)
figures out properly what is going on.
It is expected to be reverted in due course.
|
|
Add install date to logging page.
|
|
|
|
Oversight from #1958.
|
|
This implements a poor-man's build info.
See #1352. Unfortunately, that requires a separate build target, and
does not work with `cake autobuild`.
This just records the *install date* and displays that info on the
logging page. "Install date" because we can reliably determine it, and
because it does answer the question *have I upgrade Vimium on this
machine since last week?*. And on the logging page because that's out
of the way, and not part of the regular Vimium interface.
|
|
|
