Nicole Sullivan
Oooh, neato. Hadn’t seen that before. Will spelunk, this is great!
This is a really interesting approach that isn’t quite a CSS reset or a normalisation. Instead, it’s an experiment to reimagine what a default browser stylesheet would be like if it were created today, without concerns about backwards compatibility:
Applies basic styling to form elements and controls, getting you started with custom styling. We want to find the balance between providing a base for implementing a custom design, and allowing OS-level control over how form inputs work (like how a number pad works on iOS).
Provides a very lightweight starter file, with generic visual styling that you will want to replace. This isn’t as robust or opinionated as a starter-theme or framework. We’ve leaned toward specifying less, so you have less to override. (We haven’t defined any font families, for example.)
You can contribute by adding issues.
Oooh, neato. Hadn’t seen that before. Will spelunk, this is great!
Feature request, unless I missed it - link to a live demo page from the GitHub readme with an example of everything that is affected (all the heading levels, form elements etc)
This episode of the Shop Talk Show is the dictionary definition of “rambling” but I had a lot of fun rambling with Chris and Dave!
Progressive enhancement is about building something robust, that works everywhere, and then making it better where possible.
You might not need (much) JavaScript for these common interface patterns.
While we all love the power and flexibility JS provides, we should also respect it, and our users, by limiting its use to only what it needs to do.
Yes! Client-side JavaScript should do what only client-side JavaScript can do.
The core idea of the event is to get you up to speed on the most powerful web platform features that you can use right now. I love that because it aligns perfectly with what I’ve been working on over the last couple of years: finding ways to break old habits to get the most out of CSS.
Here’s a little snippet of CSS that solves a problem I’ve never considered:
The problem is that Live Text, “Select text in images to copy or take action,” is enabled by default on iOS devices (Settings → General → Language & Region), which can interfere with the contextual menu in Safari. Pressing down on the above link may select the text inside the image instead of selecting the link URL.
Reminding myself just how much you can do with CSS these days.
Have you got the perfect talk for this event? Let me know!
A one-day event all about what you can in web browsers today: Brighton, March 12th, 2026. Tickets are just £225+VAT!
How to make the distance of link underlines proportional to the line height of the text.
Make your links beautiful and accessible.
15 Likes
# Liked by Ada Rose Cannon on Tuesday, April 30th, 2019 at 8:46am
# Liked by Ollie Boermans on Tuesday, April 30th, 2019 at 10:50am
# Liked by SNDS Ent. on Tuesday, April 30th, 2019 at 10:50am
# Liked by Morgan on Tuesday, April 30th, 2019 at 11:16am
# Liked by kevin duquette on Tuesday, April 30th, 2019 at 12:40pm
# Liked by Will Worth on Tuesday, April 30th, 2019 at 1:10pm
# Liked by Grady Congdon on Tuesday, April 30th, 2019 at 1:36pm
# Liked by Emyr Thomas on Tuesday, April 30th, 2019 at 2:11pm
# Liked by L͛i͛n͛d͛s͛e͛y͛ ✌🏼 on Tuesday, April 30th, 2019 at 5:00pm
# Liked by Nicole Sullivan on Tuesday, April 30th, 2019 at 5:00pm
# Liked by Steven Lambert on Tuesday, April 30th, 2019 at 6:20pm
# Liked by Miriam Suzanne on Tuesday, April 30th, 2019 at 7:24pm
# Liked by Ryon Coleman on Tuesday, April 30th, 2019 at 8:00pm
# Liked by Tom Young on Tuesday, April 30th, 2019 at 8:00pm
# Liked by Richard Scarrott on Wednesday, May 1st, 2019 at 7:31am