<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vimium/tests/dom_tests, branch 1.54</title>
<subtitle>The hacker's browser.</subtitle>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/'/>
<entry>
<title>Simplify hint-string generation; fix tests.</title>
<updated>2016-01-28T17:06:43+00:00</updated>
<author>
<name>Stephen Blott</name>
</author>
<published>2016-01-28T17:06:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=811b3bb0280a624b6a3e17c0199ec78a1aef7e07'/>
<id>811b3bb0280a624b6a3e17c0199ec78a1aef7e07</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Block keyboard events when a filtered hint matches.</title>
<updated>2015-10-02T05:40:45+00:00</updated>
<author>
<name>Stephen Blott</name>
</author>
<published>2015-10-02T05:40:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=c9af886a92e4b686456b34949e907a9d79fb223e'/>
<id>c9af886a92e4b686456b34949e907a9d79fb223e</id>
<content type='text'>
Previously, we blocked keyboard events for a fixed 200ms.

With this PR, we continue blocking keyboard events until 150ms after the
last `keydown` or `keypress` event.  So, we wait until we think the user
has stopped typing.

Fixes #1842.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously, we blocked keyboard events for a fixed 200ms.

With this PR, we continue blocking keyboard events until 150ms after the
last `keydown` or `keypress` event.  So, we wait until we think the user
has stopped typing.

Fixes #1842.
</pre>
</div>
</content>
</entry>
<entry>
<title>Only show link hints for &lt;label&gt;s for elements without a hint</title>
<updated>2015-09-13T14:10:30+00:00</updated>
<author>
<name>mrmr1993</name>
</author>
<published>2015-09-13T14:10:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=4a28bfb221b4fed51e6badea0c9d6598393794df'/>
<id>4a28bfb221b4fed51e6badea0c9d6598393794df</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Make &lt;label&gt;s clickable with LinkHints</title>
<updated>2015-09-13T14:03:04+00:00</updated>
<author>
<name>mrmr1993</name>
</author>
<published>2015-09-13T14:03:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=940ab8d62db784c2506222d3c5c6c1117b30fea3'/>
<id>940ab8d62db784c2506222d3c5c6c1117b30fea3</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Make the sort used for filetered link hints stable.</title>
<updated>2015-09-11T06:11:49+00:00</updated>
<author>
<name>Stephen Blott</name>
</author>
<published>2015-09-11T05:53:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=4976850e975b98e20505d9a92bde4982608a18e2'/>
<id>4976850e975b98e20505d9a92bde4982608a18e2</id>
<content type='text'>
JavaScript's sort function is not stable; this PR makes the sort used for filtered link hints stable.

There are two reasons for doing this:

- High-scoring hints are more likely to keep the same hint string as the user continues typing. (Currently, the hints assigned change based on the vaguaries of the non-stable sort.)

- For equal-scoring hints, we retain the visit-child-before-parent ordering (which is used to NOT match a parent's text if we have already matched that text in a child).

And, as a result of all of that, the UX is more predictable and hence better.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
JavaScript's sort function is not stable; this PR makes the sort used for filtered link hints stable.

There are two reasons for doing this:

- High-scoring hints are more likely to keep the same hint string as the user continues typing. (Currently, the hints assigned change based on the vaguaries of the non-stable sort.)

- For equal-scoring hints, we retain the visit-child-before-parent ordering (which is used to NOT match a parent's text if we have already matched that text in a child).

And, as a result of all of that, the UX is more predictable and hence better.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'store-all-settings' into hud-iframe-input-with-store-all-settings</title>
<updated>2015-06-25T04:09:36+00:00</updated>
<author>
<name>Stephen Blott</name>
</author>
<published>2015-06-25T04:09:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=e5faeff7d48a206a080a56a6541963d2d3c86da7'/>
<id>e5faeff7d48a206a080a56a6541963d2d3c86da7</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Guard against chrome being undefined in the HUD iframe</title>
<updated>2015-06-10T16:22:21+00:00</updated>
<author>
<name>mrmr1993</name>
</author>
<published>2015-06-02T16:19:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=73c651465d1395e23daae01b0ae2a3df5b24a789'/>
<id>73c651465d1395e23daae01b0ae2a3df5b24a789</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix bug relating to duplicate hint strings.</title>
<updated>2015-06-10T15:52:16+00:00</updated>
<author>
<name>Stephen Blott</name>
</author>
<published>2015-06-10T15:39:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=61764d812a37ca2c29b3b7ddde878f25250abf81'/>
<id>61764d812a37ca2c29b3b7ddde878f25250abf81</id>
<content type='text'>
(Not sure when this crept in.)

We need to ensure that we always generate the same hint strings for the
same filter state.  Here, we do this by always using the same mechanism
(@filterLinkHints) to set the hint strings.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
(Not sure when this crept in.)

We need to ensure that we always generate the same hint strings for the
same filter state.  Here, we do this by always using the same mechanism
(@filterLinkHints) to set the hint strings.
</pre>
</div>
</content>
</entry>
<entry>
<title>Make LinkHints a class (LinkHintsMode).</title>
<updated>2015-06-09T13:47:39+00:00</updated>
<author>
<name>Stephen Blott</name>
</author>
<published>2015-06-09T13:47:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=98a3f4c96e8b189ca142f7cccbc1ef995c158b9d'/>
<id>98a3f4c96e8b189ca142f7cccbc1ef995c158b9d</id>
<content type='text'>
Functionality wise, this is a no-op.  However, since we now create a new
LinkHintsMode object on every "f", we don't need to be so careful about
resetting the state on exit.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Functionality wise, this is a no-op.  However, since we now create a new
LinkHintsMode object on every "f", we don't need to be so careful about
resetting the state on exit.
</pre>
</div>
</content>
</entry>
<entry>
<title>Remove LinkHints.init()...</title>
<updated>2015-06-01T08:46:43+00:00</updated>
<author>
<name>Stephen Blott</name>
</author>
<published>2015-06-01T08:46:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/vimium/commit/?id=e8476682362b9648aba874e8581fe9076479f734'/>
<id>e8476682362b9648aba874e8581fe9076479f734</id>
<content type='text'>
LinkHints.init() isn't doing anything.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
LinkHints.init() isn't doing anything.
</pre>
</div>
</content>
</entry>
</feed>
