The beauty is that once you understand the limitations of responsive grids, and why and when column spans break grid responsiveness, it is possible to define a responsive magazine/news style layout in just a dozen lines of code plus one simple media query (or even with no media queries if you are willing to limit your span options).
Foldable devices have brought with them talk of a ‘foldable web,’ and the idea that long-standing web conventions may be on the verge of a serious shakeup. Is it all hype, or is it time to get flexible?
TL;DR: Accessibility issues, input issues, ignoring letters, and users changing the number without realizing it by scrolling.
Using <input type=”text” inputmode=”numeric” pattern=“[0-9]*”> allows for a degree of separation between how the user enters data (“input mode”), what the browser expects the user input to contain (type equals number), and potentially how it tries to validate it.
I’ve always abided in the idea that “HTML is accessible by default and then we come along and mess it up.” But that’s not always the case. There are some cases where even using plain ol’ HTML causes accessibility problems. I’m going to start rounding up those HTML shortfalls in this here post as a little living document that I can personally reference every time I write some HTML.
Utopia is not a product, a plugin, or a framework. It’s a memorable/pretentious word we use to refer to a way of thinking about fluid responsive design. There’s no program or dependency to install, although we are developing some free tools, including the Type Scale Calculator, and the CSS Generator.
A lot of performance optimisations are easy on paper, but difficult in reality. Jake & Surma dig into look at the optimisations they made for https://proxx.app, and dig into the build tools that made them possible.
I thought this talk would go over my head, but it was really interesting, if for no other reason that seeing that I’m not alone in my fear of webpack.