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

Hi @yoavweiss -- thanks for bringing this to our attention.  Our biggest question has to do with the question of DOM modifications. You state a soft navigation "modifies the DOM" but it's not clear why this is a requirement? It seems like you're trying to make a distinction between "navigations" and "interactions", it's unclear how this subtle (and underspecified?) distinction can be reliably determined by your proposed heuristics. We can imagine that the heuristics can be defined to catch current examples but would be wrong about future applications. We wonder if simply using the navigation API should be the trigger, and then possibly provide the developer a hook to filter out navigations they don't feel are worth tracking would be more reliable?

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

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