(6) This work is never done! We are continuously adding new shortcuts, refining existing ones, and adding guardrails to prevent regressions, so more to come.
Big thanks to the entire team: @mwichary, @okaysee, Rachel Miller, @pseullah, @msfeldstein!
Last year @figma shipped keyboard shortcut support for several non-US QWERTY keyboards. The process took us on a bit of a rabbit hole 🐇 🕳️, so I wanted to share what I learned…
Read on if you love a technical challenge → https://t.co/J39GvWHtwr
(5) And all this, of course, eventually needed to be messaged back to our users—further complicated by toggling layouts and imperfect system keyboard detection.
If you're curious how we figured it out, read more in the full article: https://t.co/J39GvWHtwr
“The user is not like me”—this mantra from @cmuhcii reminds me to always build from our users’ needs.
Here’s a conversation with amazing colleagues @dorothchen, Rachel and David about what we’ve learned from the accessibility community and what’s ahead!
https://t.co/8qqW1fBvWJ
🇬🇧🇸🇪🇫🇮🇩🇰🇳🇴🇮🇹🇪🇸🌎
We've added 8 more layouts (UK, SE, FI, DK, NO, IT, ES, LATAM) so more folks can work faster in @Figma.
It's been fun to dig into ⌨️ quirks with @mwichary @dorothchen@SulaYang1 + Rachel Miller!
Sign up here if you'd like to beta test: https://t.co/Jw7otaHDN4
Been incredible to work with such talented colleagues like Rachel, @dorothchen, and David Winslow on this effort on the engineering side, and also looking forward to what’s to come!
@jensimmons If this thread is still open, I have something very specific!
There's a long-standing bug[1] where input events are fired in the wrong order. Most recently, it has been causing issues when working on Figma keyboard shortcuts.
[1] https://t.co/y3uGqoWxCY