The island below calls a card component, and the card calls a badge. Each call opens a hydration context of its own, so the data-hk the server writes on the card is 10 and the one on the badge is 110: a slot inside a slot, not a running count. The browser opens the same two contexts and finds the nodes that are already there.
the counter island | the searching island | the showcase | back to the three panels
count 5
One view! body and two #[component(client)] bodies in demo-app/island/nested.rs, compiled once by the server and once by the backend. Clicking +1 touches the count and nothing inside the components.
This paragraph is child content: it was built where the call is written and rendered into a buffer the component's own view writes back out. That is why an eager child is numbered before the component it was passed to.