It's funny how we can't rely on our intuition anymore, when the code we're reviewing is stochastically engineered to look maximally correct.

Am I the only one who dislikes hiding based on scroll direction?

You scroll slightly to far, go back up and immediately have a title bar in your face.

There's getOwnPropertySymbols, but now I feel like we're just bending the system to stop others from bending the system.

My issue isn't with performance, but readability. One of the documented use-cases for Symbols is weak information hiding, so it feels more obvious to me.

If we're trying to keep the member inaccessible outside the module, isn't this what symbols are for?

const value = Symbol()

class A {
[value]: ... // can't be accessed without the symbol
}

developer.mozilla.org/en-US/docs/W...

I hope we get to see it on YouTube eventually. Your discussions in the last 2 weeks were really helpful for finally understanding the intentions behind transitions.

What is the advantage of tying actions directly to elements, rather than having a composable hook?

I personally liked passing the pending state explicitly, since its more flexible, eg when the action is triggered from inside a menu:

<ComboBox>
<TriggerButton loading={...} />
<Content>
<Item onClick={...} />
</Content>
<ComboBox>

Suprisingly no - atleast not on npm.

npmtrends.com/jest-vs-jque...

The docs have this example, which also uses state for portal targets: react.dev/reference/re...

…right, I forgot that useRef wouldn’t trigger a rerender anyways. Maybe like this?:

```
const [el, setEl] = useState()

return <>
<div ref={setEl} />
{el && createPortal(..., el)}
</>
```

I'd probably accept the rerender, since the only duplicate work is that one portal target.

Why is useRef a problem?

The materials are all significantly less transparent. This may ofc be due to the screenshots only showing very controlled scenarios, but I take it as a sign that the current state of the beta isn't what they intended.

Also, the reduce-motion setting supposedly turns off some of the refractions.

Things that I personally like:

- Scroll edge effects solve the issue of scrollable content just disappearing into a divider, like here on Bsky. Not knowing whether a view is scrollable has been a recurring complaint in the past.

- The toolbar design finally gives all buttons clear shapes again.

They have a WWDC video explaining their rationale. IMO they're trying to address real problems.

Interestingly, the examples here have far fewer a11y-issues than the version shown at the keynote.

developer.apple.com/videos/play/...

Many packages in the React-ecosystem seem to have spiked in 2025. Other frameworks declined. I wonder what's going on...

npmtrends.com/@tanstack/re...