A collection of thoughts about HTML, CSS, JavaScript, UX, a11y, web standards, and related things. Posts by Cory LaViska.


Success Requires Luck

Written on

I've concluded that successful "makers" have one thing in common: luck.

Flash of Undefined Custom Elements (FOUCE)

Written on

Web components are defined and registered with JavaScript. Depending on how and when you load the scripts that perform registration, you may see a brief flash of unstyled HTML where your custom elements should be when the page loads. This is not dissimilar to FOUC, which occurs when HTML is displayed before the stylesheet has loaded.

Bulletproof Components

Written on

Somewhere buried in my dusty basement lives a signed copy of Dan Cederholm's classic book Bulletproof Web Design. I purchased it during my first trip to An Event Apart in 2007. This book meant a lot to me back then, and almost 15 years later, many of its concepts still hold true.

Empowering Design System Users

Written on

The question of whether or not component APIs should be locked down at the code level comes up quite a bit. For example, if a button spec only calls for primary, secondary, and tertiary variants, should we still expose parts and custom properties so users can make further customization as needed?

Exploring the EyeDropper API

Written on

The EyeDropper API has landed in Chrome and Edge 95! This is a simple promise-based API that lets you select a color from anywhere on the screen. Let's dive in and see how it works.

The Future of Frameworks

Written on

Love them or hate them, web components ("custom elements") are making a huge dent in the world of front-end development. As of today, close to 18% of page views in Chrome are registering web components. That's an insane amount of usage!

Superpowers

Written on

I stumbled upon a short post that intrigued me. In it, the author claims that the cure for boredom is superpowers. Not superpowers in the Superman sense, but ones that we can teach ourselves.

Know When To Draw The Line

Written on

One-off variations aren't uncommon, but they don't belong in your design system. You're design system isn't solving for every possible use case — it's encouraging visual consistency and efficient development. Use custom styles for one-offs.

Don't Do Magic

Written on

We recently had a design for an "alert" component with an actions slot. In the spec, only secondary buttons were allowed in it.

On Buttons and Links

Written on

I posted a tweet yesterday that was met with some controversy, so I thought it would be a good idea to unravel it.

Feeds available in Atom & JSON


Explore the archive for additional posts or press / to search.