3 ms·
A few questions I have: what happens to the host page when a portal becomes the active page? Does the host page continue to run in the background? If so, what h
by jameslk 6y ago
A few questions I have: what happens to the host page when a portal becomes the active page? Does the host page continue to run in the background? If so, what happens when you open multiple portals? I assume the predecessor host pages must stop running otherwise we run into a memory leak type of scenario?
- domenicd 6y agoThe current specification allows the portaled page to optionally "adopt its predecessor", putting it into a portal. It's not clear whether this functionality will fully survive, as we refocus portals around a more tightly scoped prerendering-focused MVP. For example predecessor adoption might only happen automatically (via the browser's already-existing back-forward cache), instead of via an explicit JS API. We'll see. Multiple portals are generally like multiple iframes, although we may also impose some restrictions on "backgrounded" portals (e.g. the automatic predecessor-adoption-into-the-bfcache mentioned above).
- deleted 6y ago[deleted]
- jameslk 6y agoThank you for this clarification