vimium/pages/logging.html, branch v1.61 The hacker's browser. Remove content_script_loader and all references to it 2017-04-17T16:36:04+00:00 mrmr1993 2017-04-17T16:36:04+00:00 93a07e4c4ccc64b5939adbf71a12bfad403845ad 






Revert "Use HTML5 import to load content scripts."
2017-04-16T14:24:35+00:00

mrmr1993

2017-02-08T19:26:46+00:00

11e4fc2e1fbb1f2c3633a7ab23dfc24eb4ca511f

This reverts commit d00345f45b5b3e56970237799c69808527e91919.

This is not (and will not be) supported by Firefox.





This reverts commit d00345f45b5b3e56970237799c69808527e91919.

This is not (and will not be) supported by Firefox.







Use HTML5 import to load content scripts.
2016-10-01T11:18:24+00:00

Stephen Blott

2016-10-01T11:05:29+00:00

d00345f45b5b3e56970237799c69808527e91919

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.





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.







Reinstate loading vimium.css.
2016-09-27T12:45:42+00:00

Stephen Blott

2016-09-27T12:45:30+00:00

59942281ce88283345a201f1bfaa76b628308472

Follow on from 8601edd71e74ba522e32658309cb2e7acca8aeeb.





Follow on from 8601edd71e74ba522e32658309cb2e7acca8aeeb.







Disable content-script loader (temporary).
2016-09-27T05:45:19+00:00

Stephen Blott

2016-09-27T05:45:19+00:00

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.





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.







Merge pull request #2014 from smblott-github/record-install-date
2016-02-28T10:14:41+00:00

Stephen Blott

2016-02-28T10:14:41+00:00

8adfa7c4ef8357b6cb945354d6da1b7b92615119

Add install date to logging page.




Add install date to logging page.






Include branch information in the logging page
2016-02-22T15:59:24+00:00

mrmr1993

2016-02-22T15:59:24+00:00

c96a11b542263d14ed0c6e0ee11de8604992e058












Correct name on the logging page.
2016-02-22T10:27:01+00:00

Stephen Blott

2016-02-22T10:27:01+00:00

efbcdea1ad25ec13d93403a3abd26da5905da732

Oversight from #1958.





Oversight from #1958.







Add install date to logging page.
2016-02-22T10:12:00+00:00

Stephen Blott

2016-02-22T10:11:52+00:00

251496451907801c45b4b794a235030e6ab99ae2

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.





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.







Add a basic log page
2016-01-30T13:07:14+00:00

mrmr1993

2016-01-30T13:00:53+00:00

91fb337c9d92f6291ef42c55c4d29ca35b710203