About 11ty kilograms, I reckon?
About 11ty kilograms, I reckon?
slow is steady, steady is fast
Still an interesting exploration!
If you're iterating… why not use clamp() for fluid sizing?
Also I'm curious: do you really get away with h-element selectors in the systems you've worked on? Or is this just for simple WYSIWYG pages? H-level and visual style seldom match in my components/systems.
…maybe? I don't quite see the actual benefit of coalescing it to one line, if you ask me. It's sweet but comma-separated selectors work. I'd rather we push for `for()` in CSS custom functions so we can loop through things without getting sassy.
It is neat – but it is also restricted to "In a typical demo where h1 through h6 are siblings in order", right? 🤔
/cc @sturobson.com
Not to mention „JudgeGPT“.
Love the new name, it‘s spot on!
I expected no Less.
That sounds very reasonable.
It‘s also all quite unexpected when you‘re following a screen reader, where 'invisible' details like “link menu“, the round-trips and page loads, etc. become more apparent.
That said: All is fair in love and on personal pages. You can just do things!
Did the two of you discuss also wrapping the <ul> in a <nav>?
I assume it‘s not necessary/redundant if the dialog is labelled? 🤔
The <ul> looks so… naked to my trained-in-certain-way eye.
66° North
Have you done a comic about logical properties yet? margin-block-start, padding-inline-end instead of margin-top and padding-right?
developer.mozilla.org/en-US/docs/W...