The latest updates on your projects. Learn more aboutVercel for Git ↗︎

This will break any tutorials that involvenavigation.type, no?

(I think we should undo#181 and work on this at leisure, rather than leaving the current UI in place any longer)

What do you mean bynavigation.type?
(if you're nervous keeping the current state active we can do revert first if you want)

InbeforeNavigate andafterNavigate etc —navigation.type should bepopstate but will belinkhttps://kit.svelte.dev/docs/types#public-types-navigationtype. I'll do the revert, then we can figure this stuff out later

Ah I see. We could

• just not worry about this case in the respective tutorial
• specifically disable the pushState hack and use pop/push delta commands instead ofgoto for that tutorial
• disable the pushState hack and use pop/push delta for all tutorials (with the drawback that it pollutes the parent history like before)

I don't think that should hold us back though, since without this feature there wouldn't even be a way to trigger thepopstate navigation type within the iframe.

@dummdidumm@Rich-Harris Another idea could be to allow the iframe state to work naturally until we see some movement onwhatwg/html#6501. That meaning, we could mesh the iframe history with the window's history and have window preserve the iframe state by storing the iframe's current path in a URL param, like…

https://learn.svelte.dev/tutorial/pages?path=/about

That way, it's not so much pollution as it is standard history tracking where there are no redundant polluted entries, but a bunch of unique entries that are all meaningful when they occur.