vimium, branch v1.62 The hacker's browser. Bump to v1.62. 2017-12-09T09:42:59+00:00 Stephen Blott 2017-12-09T09:42:59+00:00 7ac0e2df1054105a4edfb9d241a65ba2b83f2545 






Merge pull request #2852 from smblott-github/no-clipboardWrite-in-chrome-version
2017-12-09T09:41:25+00:00

Stephen Blott

2017-12-09T09:41:25+00:00

ba21230e29b9d4438fa6338d914c0616e253d084

No clipboardWrite permission for Chrome Store version.




No clipboardWrite permission for Chrome Store version.






Merge pull request #2853 from mrmr1993/pr/link-hints-only-activated-frames
2017-12-03T14:43:48+00:00

Stephen Blott

2017-12-03T14:43:48+00:00

9b823db6aa871e18679fb13d9772eccaccfe2393

Small tweaks for popup message code




Small tweaks for popup message code






Only send link hints messages to frames which have registered
2017-12-02T18:49:42+00:00

mrmr1993

2017-12-02T18:49:42+00:00

f32dfbfc650a873d1f91ac3fb21383fb02423c7f

This puts link hints frame behaviour back to matching
fb00eaa6bd4ee8889d10a9ef9d976fefd3be7879

In particular, we go back to not sending link hints messages to frames
that are too small (according to DomUtils.windowIsTooSmall).





This puts link hints frame behaviour back to matching
fb00eaa6bd4ee8889d10a9ef9d976fefd3be7879

In particular, we go back to not sending link hints messages to frames
that are too small (according to DomUtils.windowIsTooSmall).







Show browser-blocking complaint in the popup for empty portForTab object
2017-12-02T18:42:35+00:00

mrmr1993

2017-12-02T18:42:35+00:00

601aad57c843ff1368c5a9e152ea609431cac1a0

To test the difference:
* load an unblocked URL (e.g. https://www.example.com) in a tab
* open the popup, see that the exclusion rules show as expected
* navigate the tab to a blocked URL (e.g. chrome://extensions)
* open the popup again

Before this commit, the popup still shows the exclusion rules, because
there is still a portForTabs object associated with the tabId.

This commit adds a second check to see if the object is empty, and the
message shows as expected, because all of the ports have been closed and
cleared from the object.





To test the difference:
* load an unblocked URL (e.g. https://www.example.com) in a tab
* open the popup, see that the exclusion rules show as expected
* navigate the tab to a blocked URL (e.g. chrome://extensions)
* open the popup again

Before this commit, the popup still shows the exclusion rules, because
there is still a portForTabs object associated with the tabId.

This commit adds a second check to see if the object is empty, and the
message shows as expected, because all of the ports have been closed and
cleared from the object.







Ensure that a port can only unregister its frameId if it's associated
2017-12-02T18:38:53+00:00

mrmr1993

2017-12-02T18:38:53+00:00

ff615efa9a41f1de5df1a6eea0e8a3c809f91b4b

This is a more complete fix for issue #2125.





This is a more complete fix for issue #2125.







No clipboardWrite permission for Chrome Store version.
2017-12-02T16:13:15+00:00

Stephen Blott

2017-12-02T16:13:15+00:00

9c36c62fc881f923ee94a72cde95a1094a12723f












Fix link hints.
2017-12-02T15:46:53+00:00

Stephen Blott

2017-12-02T15:46:51+00:00

b3fae0963056c085630c52609d11a048c5901bad

43c7390f987fea063e7a97cd8b37c7b61d45f615 inadvertently broke link hints.

Mention @mrmr1993.





43c7390f987fea063e7a97cd8b37c7b61d45f615 inadvertently broke link hints.

Mention @mrmr1993.







Use portsForTab to decide whether Vimium can access a tab or not
2017-12-02T15:02:43+00:00

mrmr1993

2017-12-02T15:02:43+00:00

fb00eaa6bd4ee8889d10a9ef9d976fefd3be7879












Register ports for all frames that open them
2017-12-02T14:57:20+00:00

mrmr1993

2017-12-02T13:32:10+00:00

43c7390f987fea063e7a97cd8b37c7b61d45f615