A story of a Figma bug that wasn't a bug at all (2021)

> So the engineers came up with a power-user shortcut… and since the Shift was a natural counterpart in the Caps Lock world, it could also do the same here!

> The solution: you could hold Shift and press the arrow/numeric key to quickly reverse its current mode.

One person's "ingenious" is another's "confusing due to lack of clarity". If I hit some keys that weren't numlock and they caused my numpad to behave differently than the mode I expected, I would not think "oh wow that's so clever", I would be confused about what happened and probably not understand how to use that mechanism from observing the surprising behavior.

I guess it was a figma of our imagination.

It's interesting in retrospect that the keyboard of the first Macintosh was a very deliberate 60% layout, given how popular that size has become over the past 15 years among enthusiasts (albeit now augmented by fully customizable secondary layers so arrow keys/etc are still possible).

This is the first time, in my entire life I have experienced a website overriding pinch to zoom. I couldn't pinch to zoom, just on top of pictures, which would expand the image then zoom into it.

Why would the author do that, very frustrating.

loved it!

I'm sorry, but it doesn't matter what IBM did in the 70s and 80s with keyboards, if shift+2 changes the zoom for everyone but a windows user using the number pad, thats a bug. Its a violated expedition and different between OSes.

Also, what is this writing style. Every sentence is numbered with options to tweet it, horizontal lines between each with huge amounts of padding and one to two images between each sentence. Is this even meant to be read by humans?