benface

And Firefox! I actually went back to Firefox for this reason.

I suggest replacing Paste with Raycast’s clipboard history since you already use that, and Bartender with the free and open source Ice.

Suggestion: `throws` clause and typed catch clause · Issue #13219 · microsoft/TypeScript The typescript type system is helpful in most cases, but it can’t be utilized when handling exceptions. For example: function fn(num: number): void { if (num === 0) { throw "error: can't deal with ...

100%. Unfortunately not going to happen: github.com/microsoft/Ty...

I just call it “global styles”.

This cannot come to Safari and Firefox fast enough!

It's Spagett! | Tim and Eric Awesome Show, Great Job! | Adult Swim YouTube video by Adult Swim Deutschland

youtu.be/Omy3BERUd1g

That’s Spaghett!!! Spoogy

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.

It was a lovely show!

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()`?

What is this printer?

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?

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. 😒

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.”

What about SVG <title>s?

Nope, same here.

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.

🥲 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?

When will you tell us?

Nothing. It looks great to me.

Wow! I guess I’m an OG.

It came out in 2017 👴

Would love a blog post on those approaches 😁