Re: [w3ctag/design-reviews] Soft Navigations (Issue #879)

Thanks for taking a look.

I added a [goals](https://github.com/WICG/soft-navigations#goals) section to the explainer that clarifies some of the constrains around the design.



> You state a soft navigation "modifies the DOM" but it's not clear why this is a requirement?

That's a great question. I've ran a bunch of experiments, and this seemed to align well with SPAs today. But it is possible that the heuristic will evolve as part of the Origin Trial, or given this [reported issue](https://github.com/WICG/soft-navigations/issues/8). 



> We wonder if simply using the navigation API should be the trigger

The Navigation API doesn't provide any more guarantees than the History API did regarding what is and isn't an actual navigation.

 

> possibly provide the developer a hook to filter out navigations they don't feel are worth tracking would be more reliable

The newly added [goals] section should clarify why that strategy will not work well for the use case.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/879#issuecomment-1707991589
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/879/1707991589@github.com>