Published inITNEXTBrowsers need a “some JS” modeUsers need more options than all or none for enabling JavascriptApr 9A response icon1Apr 9A response icon1
Published inITNEXTFixing Focus for SafariIn 2008, Apple’s Safari team had a problem: web developers had noticed that links, buttons, and several input elements were not matching…Nov 16, 2021A response icon2Nov 16, 2021A response icon2
Published inUX CollectiveIt’s time we say goodbye to pixel unitsWhy responsive and accessible websites don’t really need ‘em.Jan 27, 2021A response icon15Jan 27, 2021A response icon15
Why JS needs native memoizationI have a proposal for a new feature for JavaScript: built-in memoization. Let’s make Function.memoize a reality.Jan 4, 2021A response icon1Jan 4, 2021A response icon1
Accessible Fluid TypographyScreen-relative units, like vw and vh, are not accessible by themselves. Pair them with relative units to respect the user’s preferences.Dec 30, 2020A response icon2Dec 30, 2020A response icon2
When Should You Do A Rewrite?Everyone wants to rewrite their codebase. The current one has too much cruft. It’s legacy code. Ugh. But when is it cost-effective?Oct 3, 2019Oct 3, 2019
JavaScript’s Next Evolution: “use stricter”;“use strict”; greatly cleaned up JavaScript, but there are still some pain points to eliminate. I think we’re ready for “use stricter”;Sep 6, 2019Sep 6, 2019
Magic Numbers in CSSOne of my more common critiques on code reviews of CSS changes is the presence of magic numbers. I’ll see a property being added with a…Jul 29, 2019Jul 29, 2019
Published inITNEXTWhy I Don’t Use CSS VariablesCSS variables, officially called Custom Properties, are amazing. I want to use them, but I can’t. Because IE11 doesn’t support them.Jun 19, 2019A response icon2Jun 19, 2019A response icon2
Why NaN !== NaNAmong the many seeming oddities of JavaScript is the fact that NaN (Not-a-Number) is not equal to itself. This is a FEATURE of JavaScript.May 14, 2019A response icon1May 14, 2019A response icon1
