vimium/tests, branch v1.60 The hacker's browser. Check whether events are trusted before executing listeners 2017-08-18T17:51:45+00:00 mrmr1993 2017-08-18T17:41:51+00:00 d946a98df10bf1ae5bb02e5cd7eaa2a0c3a06aad 






FF - Fix updates from the exclusions popup
2017-04-30T23:15:51+00:00

mrmr1993

2017-04-30T23:15:51+00:00

9a1b56a899575d71e07eb3466e5fbf16d5a18571

This stops |Exclusions| from holding a reference to the |value|
parameter passed to |Settings.set|. In Firefox, this object is garbage
collected when the owning context (the exclusions popup) is closed.

The fix for all such cases in the future is to switch to using
|Settings.get|, which implicitly does |JSON.parse JSON.stringify value|
and thus returns an object in the same context as |Settings|.

We could fix this generally by doing this for the
|Settings.performPostUpdateHook| call in |Settings.set| instead.
However, I'm not convinced that it warrants the overhead of a
|JSON.parse| for every |Settings.set| call.





This stops |Exclusions| from holding a reference to the |value|
parameter passed to |Settings.set|. In Firefox, this object is garbage
collected when the owning context (the exclusions popup) is closed.

The fix for all such cases in the future is to switch to using
|Settings.get|, which implicitly does |JSON.parse JSON.stringify value|
and thus returns an object in the same context as |Settings|.

We could fix this generally by doing this for the
|Settings.performPostUpdateHook| call in |Settings.set| instead.
However, I'm not convinced that it warrants the overhead of a
|JSON.parse| for every |Settings.set| call.







Remove use of keyCodes entirely.
2017-04-18T04:50:51+00:00

Stephen Blott

2017-04-13T13:57:26+00:00

d03845e3151babbd63cf13e9e3d74d98351671f9

event.keyCode` is depricated:

  - https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyCode





event.keyCode` is depricated:

  - https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyCode







Rework tests for all key handling on keydown.
2017-04-18T04:50:51+00:00

Stephen Blott

2017-04-13T13:09:14+00:00

8e4119f84bbde748eb595e6766dbb47a6cd0133c












Remove stub for deprecated onActiveChanged
2017-02-08T18:05:00+00:00

mrmr1993

2017-02-08T18:04:28+00:00

992149b64edf264fcd86179a2ba0f4d741f3cddd












Remove stub for deprecated tabs.onSelectionChanged
2017-02-08T18:01:26+00:00

mrmr1993

2017-02-08T18:01:26+00:00

47ba34083e229293753854dab32bf03947caea6b












Merge pull request #2326 from smblott-github/move-search-engines-to-bg-utils
2016-12-10T10:51:57+00:00

Stephen Blott

2016-12-10T10:51:57+00:00

bd06c7ccfbfcf36e6d15fba72b7af90254b05da2

Move SearchEngines to bg-utils.coffee.




Move SearchEngines to bg-utils.coffee.






Tweak #2338.
2016-12-10T10:32:13+00:00

Stephen Blott

2016-12-10T10:32:13+00:00

856f0ff8b35a66ecfa8a77ae41f4b761c1b1951c












treat select element as an input, setting focus to it
2016-11-09T16:23:48+00:00

Ramiro Araujo

2016-11-09T16:23:48+00:00

c5d6b80cb6eae99aed461e20c99a286eaf352a2a












Move SearchEngines to bg-utils.coffee.
2016-10-23T15:50:51+00:00

Stephen Blott

2016-10-23T15:50:48+00:00

24a6217f26911ba4e934f4a7bff8bcd30c227163

`SearchEngines` was previously in `utils.coffee`, which means it was
loaded in *every* content frame.  This is unnecessary, since it is only
used on the background page.  So this PR moves it there.

Also:

- Simplify some unnecessarily complex logic in `vomnibar.coffee`.
- Re-use `Utils.parseLines()` to parse the custom search engine configuation text.





`SearchEngines` was previously in `utils.coffee`, which means it was
loaded in *every* content frame.  This is unnecessary, since it is only
used on the background page.  So this PR moves it there.

Also:

- Simplify some unnecessarily complex logic in `vomnibar.coffee`.
- Re-use `Utils.parseLines()` to parse the custom search engine configuation text.