Some very smart ideas in here for resetting default browser styles, like only resetting lists that have classes applied to them:
ul[class],
ol[class] {
padding: 0;
}
I select only lists that do have a
classattribute because if a plain ol’<ul>or<ol>gets used, I want it to look like a list. A lot of resets, including my previous ones, aggressively remove that.
If we were to follow Jiro’s and his apprentices’ journeys and imagine web development the same way then would we ask of our junior developers to spend the first year of their career only on HTML. No CSS. No JavaScript. No frameworks. Only HTML. Only once HTML has been mastered do we move onto CSS. And only once that has been mastered do we move onto JavaScript.
This looks like a really interesting proposal for allowing developers more control over styling inputs. Based on the work being done the customisable select element, it starts with a declaration of appearance: base.
This describes how I like to work too.
If you like the prospect of an old man ranting at clouds, this is for you.
CSS wants you to build a system with it. It wants styles to build up, not flatten down.
Truth!
Safari 18 supports `content-visibility: auto` …but there’s a very niche little bug in the implementation.
Try writing your HTML in HTML, your CSS in CSS, and your JavaScript in JavaScript.
A genuinely inspiring event.
Had you heard of these bits of CSS? Me too/neither!
Going back to school in Amsterdam.
1 Like
# Liked by Aaron Parecki on Thursday, October 3rd, 2019 at 11:46am