szurubooru.git/client/js/controls/auto_complete_control.js, branch master

client/search: fix autocomplete for composite queries

2020-08-22T14:17:59Z

Fixes #342

client+server: implement code autoformatting using prettier and black

2020-06-06T12:58:23Z

client/js: format code to ESLint

2020-06-04T23:02:33Z

remove tags.json

2017-10-01T19:48:00Z

client/search: escape : in tag search

2016-09-29T20:47:41Z

client/general: fix autocomplete control

2016-08-23T21:14:21Z

Regression from d5e197e.

client/general: add empty href for link buttons

2016-08-21T23:40:30Z

In e464e69 I removed href='#' but I noticed that it broke some things. Readding href serves two purposes: - it makes links reachable with Tab key - it makes links clickable with Enter key The alternative to this approach was to introduce [tabindex] and [role] attributes. But not only using tabindex=0 with is questionable, it'd require adding a keyboard handler that'd intercept space and return key presses and simulated link clicks. Since it's best to leave this kind of thing to the native UI, I went with readding hrefs instead. I believe that hash hrefs, even though being a common practice, are silly, so I decided to settle down with empty hrefs. As a bonus, I added a snippet that prevents middle mouse clicks from opening such links/buttons in new tabs, which was the motivation for e464e69.

client/general: remove faux href='#' from links

2016-07-30T21:12:31Z

client/tags: fix hovering over autocomplete in FF

2016-07-05T21:59:10Z

Hovering over an autocomplete box always selected the last element rather than the element under the cursor. This is because resultIndex was bound by reference. This looks like a bug in FF implementation of "for (let [x, y] of ...)" -rather than binding "x" and "y" to the scope of the loop, it's equivalent to "for (var [x, y] of ...)", which causes nasty anomalies for functions created inside the loop body.

client/general: handle spaces in autocomplete

2016-07-03T17:38:17Z