Relative timestamps can cause you to feel that things are especially
interesting because they are happening "right now"; the effect is
lessened if you see absolute timestamps instead.
This fixes#2011
* 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
fixes#1884
If "disable entire toot area" is on, then the cursor becomes default between the buttons, and clicking does nothing. If it is off (default), then the cursor is always pointer and clicking between the buttons clicks the whole toot.
On the Nexus 5 especially, this ensures we no longer have nearly so many
"long tasks" (i.e. responsiveness is better). It moves html-to-txt
calculation to the same step as blurhash decoding, where it can be done
in requestIdleCallback (heck, maybe someday it could just be done in a
worker thread as well).
The `.card-title` element carries `text-overflow: ellipsis`, (and
`white-space: nowrap`), resulting in the last part of long article
titles not being visible. By adding it to the `title` attribute,
one can see the full title on hovering without having to visit the
article first.
The main concern I had was that the text is now technically
duplicated in the source code, and for short titles, also in the
UI. The primary concern there, however, was screen reader users
getting duplicate announcements. However, I believe the title
attribute is not announced by screen readers, which this (old)
article seems to confirm:
https://developer.paciellogroup.com/blog/2010/11/using-the-html-title-attribute/
That leaves the following two disadvantages:
- This doesn't solve anything for mobile users, who will still
have to follow the link to see the full title.
- Desktop users can however a (non-truncated) title to see the same
title again.
* fix: return focus to sensitive media button
fixes#1517
* additional fix for media sensitive focus
* fix audio/video name in aria-label of button
* fix hotkeys
* fix: move blurhash worker operations to before status rendering
* slight refactor
* avoid sending encoded data back and forth
* move cache outside worker
* chore(npm): Install blurhash
* feat(media): Show blurhash
* fix(media/blurhash): Better sensitive video handling
* feat(media): Preference for using blurhash
* chore(utils/blurhash): Add performance marks
* fix(utils/blurhash): Performance marks
* fix(utils/blurhash): Use correct dimension
* refactor(utils/blurhash): Use constant for number of pixels
* refactor(media): Simplify logic for displaying blurhash
* chore(tests/spec): Attempt to adjust sensitivity tests for blurhash
* chore(tests/spec): Update sensitivity tests for blurhash
* chore(tests/spec): Check for sensitive
* fix(media/blurhash): Handle videos
* fix: Video handling
* fix: Videos
* minor refactoring, fix Svelte warning
* fix: Large inline images and videos
* feat(settings): Rename blurhash setting
* refactor: Use toBlob, block media rendering until blurhash ready
* refactor: Move computations to Web Worker
* fix(workers/blurhash): More error handling
* feat(workers/blurhash): Use quick-lru for caching
* fix: Don't create Context2D needlessly
* fix(workers/blurhash): Increase cache size to 100
* fix(workers/blurhash): Don't resolve promise twice
* fix(utils/decode-image): Ignore data URLs
Throws exception which prevents the image from loading.
