benface
@benface.com
Wrong. The cascade is how CSS determines which declaration wins when there are conflicting rules. It takes multiple factors into account (origin, specificity, source order), none of which is inheritance.
November 30, 2025 at 5:20 PM
Wrong. The cascade is how CSS determines which declaration wins when there are conflicting rules. It takes multiple factors into account (origin, specificity, source order), none of which is inheritance.
I mean, `if()` is pretty powerful regardless of the naming IMO! But when you combine it with `revert-rule` then it is a true game changer.
October 27, 2025 at 3:26 PM
I mean, `if()` is pretty powerful regardless of the naming IMO! But when you combine it with `revert-rule` then it is a true game changer.
This! And typed counters too!
August 3, 2025 at 4:49 PM
This! And typed counters too!
Amazing. On a slightly related note, can we please have a way to get the `<number>` value of a counter so we can use it in `calc()`?
August 3, 2025 at 4:47 PM
Amazing. On a slightly related note, can we please have a way to get the `<number>` value of a counter so we can use it in `calc()`?
Oh so you’re talking about the spelling? I thought you meant the pronunciation. But I actually like “M-dash” because it’s what the “em” is for – the width of the letter M.
July 7, 2025 at 12:59 AM
Oh so you’re talking about the spelling? I thought you meant the pronunciation. But I actually like “M-dash” because it’s what the “em” is for – the width of the letter M.
Isn’t it exactly what it is?
July 7, 2025 at 12:48 AM
Isn’t it exactly what it is?
This probably is an edge case? I’m guessing no other page / element has these text styles.
July 6, 2025 at 4:03 PM
This probably is an edge case? I’m guessing no other page / element has these text styles.
This. MacOS Calendar has supported an arbitrary number of alerts since forever but iOS is still restricted to two. 😒
July 4, 2025 at 1:29 PM
This. MacOS Calendar has supported an arbitrary number of alerts since forever but iOS is still restricted to two. 😒
Do you mean that it can be used without a form? An example would be nice!
July 3, 2025 at 1:05 PM
Do you mean that it can be used without a form? An example would be nice!
Ah: “If <title> is within an <svg> component, then there is no special behavior, because in this context it doesn’t represent the document’s title but rather is an accessibility annotation for that SVG graphic.”
May 30, 2025 at 9:03 PM
Ah: “If <title> is within an <svg> component, then there is no special behavior, because in this context it doesn’t represent the document’s title but rather is an accessibility annotation for that SVG graphic.”
I just tested and the state is indeed reset. It seems to be per _element_, not per component.
May 19, 2025 at 5:25 PM
I just tested and the state is indeed reset. It seems to be per _element_, not per component.
> I think you can have Wrapper know what to render / how to render. The component hierarchy stays the same but the outcome changes.
But won’t there be the same issue inside Wrapper? At some point, something has to render a different element.
But won’t there be the same issue inside Wrapper? At some point, something has to render a different element.
May 19, 2025 at 3:15 PM
> I think you can have Wrapper know what to render / how to render. The component hierarchy stays the same but the outcome changes.
But won’t there be the same issue inside Wrapper? At some point, something has to render a different element.
But won’t there be the same issue inside Wrapper? At some point, something has to render a different element.
🥲 So what’s the solution? Or is conditional wrapping just bad (when it’s dynamic at least)?
May 19, 2025 at 2:39 PM
🥲 So what’s the solution? Or is conditional wrapping just bad (when it’s dynamic at least)?
Ok, I understand the potential problem, but how would you prevent it if you really do want a component to conditionally wrap children in another? Just render in a `<div>' wrapper instead?
May 19, 2025 at 1:58 PM
Ok, I understand the potential problem, but how would you prevent it if you really do want a component to conditionally wrap children in another? Just render in a `<div>' wrapper instead?
Nothing. It looks great to me.
May 18, 2025 at 11:28 PM
Nothing. It looks great to me.
Would love a blog post on those approaches 😁
April 28, 2025 at 10:43 PM
Would love a blog post on those approaches 😁
That is super clean, but what if new data needs to be fetched when the filters change? That’s harder to model in my head than pre-RSC, but I’m sure I’m missing something.
April 28, 2025 at 10:34 PM
That is super clean, but what if new data needs to be fetched when the filters change? That’s harder to model in my head than pre-RSC, but I’m sure I’m missing something.
Because Apple doesn’t allow alternative browser engines on iOS :/
April 14, 2025 at 2:23 PM
Because Apple doesn’t allow alternative browser engines on iOS :/