v1.17.0
1.17.0 (2020-05-23)
Features
Smarter focus ring behavior
The main feature of the new release is that we now use the :focus-visible
web standard to detect whether you're using the keyboard, mouse, or touchscreen and show/hide the focus ring accordingly. For mouse users, this means that the focus ring will appear much less often, which should be less visually distracting. For keyboard users, nothing should change.
If you prefer the old behavior, you can go into the settings and enable "Always show focus ring." In the future, browsers should allow users to set this at the OS or browser level so that it can automatically work for all websites. (This is already in progress for ChromeOS.)
Performance improvements
Faster thread loading
When you click a status to view its thread, the thread should load more quickly now. In most cases, the status will appear instantly, and the replies will load afterwards. This also fixed a bug where, as new statuses arrive, they weren't necessarily presented in the same order that the Mastodon frontend would show them. In addition, there should be more consistent fade-in animations.
- lazy-load the thread context (#1774) (836b0e3), closes #898
- lazy-lazy-load the :focus-visible polyfill (#1785) (f080148)
- use OffscreenCanvas in Chrome 82+ (#1779) (ea13158)
Bug Fixes
CSS tweaks
The design of the navigation header and the "indicator" (i.e. the thing that moves around as you change columns) has been tweaked to be a bit more consistent, and to make the indicator more prominent. You probably won't notice the difference, but it was driving me nuts.
- css cleanup of nav-related variables (#1786) (bedb636)
- ListItem should have proper fade animations (#1771) (c610a25)
- tweak indicator design again (#1789) (ceff1f1)
- tweak nav indicator so it's a bit more prominent (#1788) (1fc1410)
- use attr rather than class for focus-visible polyfill (#1778) (beade4a), closes #1777