By changing the shape it means no matter what the colour difference between
pressed and non-pressed it'll be possible to know the state.
Co-authored-by: Nolan Lawson <nolan@nolanlawson.com>
* feat: implement word filters
* fix: more progress on word filters
* fix: more progress
* fix: more work
* fix: more work
* fix: more progress
* fix: tweaks
* fix: basic crud stuff
* fix: more work
* test: add tests
* test: more test
* fix: handle filter expiry correctly
* fix: implement more efficient word filter logic
* fix: better required labels
* test: fix test
* test: use mastodon 3.3.0 for testing
* test: fix test
* test: fix test
* test: fix test
* test: fix test
* test: revert test change
* test: use ruby 2.6.6
* first attempt
* progress
* working
* working
* test timeago
* rm
* get timeago working
* reduce size
* fix whitespace
* more intl stuff
* more effort
* more work
* more progress
* more work
* more intl
* set lang=LOCALE
* flatten
* more work
* add ltr/rtl
* more work
* add comments
* yet more work
* still more work
* more work
* fix tests
* more test and string fixes
* fix test
* fix test
* fix test
* fix some more strings, add test
* fix snackbar
* fix }
* fix typo
* fix english
* measure perf
* start on french
* more work on french
* more french
* more french
* finish french
* fix some missing translations
* update readme
* fix test
`/` is a well-known vi/vim key-binding for search. It is supported by
Firefox for a 'quick find' feature in addition to the main find feature
available with the Ctrl+F key combination. DuckDuckGo also supports the
key to focus the search bar as well.
Signed-off-by: shine <4771718+shinenelson@users.noreply.github.com>
* fix: improve autosuggest a11y
some progress on #1629
- works in Chrome on NVDA now
- works in Chrome on VoiceOver now
- shorter aria-labels, don't repeat information like "1 of 3", because
it causes the screen reader to speak too frequently, e.g. when the
selected result hasn't changed but the number of results has. Also both
NVDA and VoiceOver already speak this information
- stop doing a fancy fade animation, just show and hide the input
instantly. I worry it confuses screen readers to have the aria-hidden
attribute in there at all
- stop using a single id to identify the active descendant - give
immutable IDs and then update the aria-activedescendant instead. I think
this is what fixed Chrome.
* fix test
