joshtumath

4 ms·

1.
by joshtumath 8mo ago
Well that's just one example. Most websites have problems. Especially on mobile viewports.
2.
by joshtumath 8mo ago
Actually I don't think the explainer gets into the full story. The reality is it's not CSS's problem. It's the browsers that have historically made text scaling weird on each platform that they support. And now just like
3.
by joshtumath 2y ago
I've just posted another blog post to provide context and answer some questions people had. Like why are we checking screenX === 0 in the first place? Why do we want different behaviour depending on keyboard or mouse inputs? And I&#x27
4.
by joshtumath 2y ago
Actually that is what we're going to do. I'm hoping to merging in code, soon, that will change it to use pointerId === -1 and then fall back to screenX === 0. At the time this code was originally written four years ago or whenever
5.
by joshtumath 2y ago
I omitted that code to keep the article simpler. We want to turn off the animation on keyboard, and move the focus to different things depending on if it's a keyboard or pointer user.
6.
by joshtumath 2y ago
Well said! It certainly applies to web development as well. Sadly, sometimes more complex solutions are needed - especially when based on user research.
7.
by joshtumath 2y ago
I am the author. > The first mistake the developer made, was that he wanted to create a different user experience between keyboard and mouse. Stick to what you get by default and design your components so they work for both usecases. We
8.
by joshtumath 2y ago
Hello I am the author and, yes, I totally agree some generic 'trigger' event would be far better. To use the keydown event means we have to assume that the 'Enter' and 'Space' are the only keys we need to check
9.
by joshtumath 2y ago
Hello I am the author and that was indeed a mistake. Whoops!