| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This commit is a bit misleading because the work here
actually replaced an attempt at using .select().
|
|
|
|
Some code paths knida just take us here no matter what's
actually entered into the input, so it's easiest to just
dismiss empty queries every time.
|
|
|
|
|
|
HTMLInputElement: selectionchange still not available, boo hoo
although this is probably appropriate wrt selection moving
literally anywhere else - should also cancel focus-first-result
|
|
|
|
...rather than tracking value changes, which is finnicky and
broke how we detected pressing enter/return to acivate search
(on 'change' event)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #551
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Somehow...
|
|
|
|
|
|
|
|
|
|
Was trying to address a bug that is already handled just by
making sure the generated search is up to date w/ search-spec lol
|
|
Turns out this is necessary for the changelog. Wow.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
