See the prerendering browsing context explainer's section on this for more information. However, because the portaled content is rendered in a prerendering browsing context, many APIs will treat the rendered content as non-visible. Like iframes, portals can render their contents inline in another document. In those cases, no message events will be sent to window.portalHost, and () will not deliver any message. */ ) Ĭross-origin portaled content cannot communicate with its embedder, as doing so would allow cross-site tracking. addEventListener ( 'portalactivate', e => ) window. Summary of differences between portals and iframesĪ document can include a element, which prerenders the specified URL in the portal:.
This makes them suitable for seamless navigations, not just instant ones for example, they enable web-developer-controlled navigation transitions between the referring page and the prerendered page. They go beyond basic prerendering support by also providing the inset preview of the content. Portals are part of a general effort toward privacy-conscious, well-specified prerendering. In particular, we propose a new HTML element which enables a page to show another page as an inset, and then activate it to perform a seamless transition to a new state, where the formerly-inset page becomes the top-level document. Portals enable seamless and instant navigations between pages.
0 kommentar(er)
