Define reconnection for cross-page navigation on presenting user agent about presentation-api

[schien]

I would vote for the third one: terminate the presentation. For complex use case that requires navigation across pages, developer can embed iframe in the presenting page.

[mfoltzgoogle]

I agree that it's not required to support navigation in the presenting page. We may want to permit navigation between fragment identifiers within the same document; this should be implemented as a re-rendering of the same document and does not trigger a load of a new document [1].

Are there any objections to the proposal from @schien to prohibit navigations between documents in the presenting browsing context?

[1] https://html.spec.whatwg.org/#scroll-to-fragid

[tidoust]

Re-reading this issue,

I would rather reformulate this in terms of "terminating the presentation when the receiving browsing context is unloaded", rather than "terminating the presentation when the page navigates to a different URL".

In particular, on top of fragments, it is common for apps to call pushState and replaceState to update the current URL without reloading the page.

[mfoltzgoogle]

That makes sense. When I was looking at this earlier, I didn't find a way to allow navigation among fragment identifiers. The flag I would set on the receiving browsing context [1] would seem to prohibit all top level navigations, even among fragment identifiers.

[1] https://www.w3.org/TR/html5/browsers.html#sandboxed-top-level-navigation-browsing-context-flag