Luke

> @lukechu10 i can work on this Great! Let's me know if you run into any issues.

The problem is that the attribute is being re-set (difference from reset) during hydration which causes the resource to be fetched again. If cache is disabled, that triggers another network...

A really simple fix might just be to make the following code only run when hydration has completed, just like what is being done in `HydrateNode::append_child`. https://github.com/sycamore-rs/sycamore/blob/abd556cbc02047042dad2ebd04405e455a9b11b2/packages/sycamore-web/src/hydrate_node.rs#L170-L173 To test that...

Thanks, but I'm not sure if this actually works. If there are conflicting `data-hk` in the DOM, when we call `querySelector("[data-hk=...])`, which node we get is undefined (or at least...

> The best solution is actually to just call `Element::querySelector` (from the root element of the hydration) instead of `Document::querySelector`. That will ensure that there's no duplicate and it'll even...

Also please let me know if you would still like to work on this.

> I'll give it a try. Will let you know if I'm stuck! Are you still working on this? If you're not, please let me know and I can take...

Superseded by #679

Generally I would just recommend hoisting your `Router` to the top of your `App` so that everything gets rendered under the `Router`. Is there a reason why you can't do...

This shouldn’t be too difficult I don’t think. I think the biggest drawback would be that we would need to enable a bunch of features on `web-sys` for all the...