The explainer refers to a new attribute for iframes instead of a new element. Can you elaborate on this?
On Wed, Aug 26, 2026, 5:23 PM Joey Arhar <[email protected]> wrote: > *Contact emails* > [email protected] > > *Explainer* > https://github.com/WICG/persistent-iframes > > *Specification* > *No information provided* > > *Summary* > Persistent widgets are embedded browsing contexts, like iframes, but they > can persist across same-origin navigations without reloading. Persistent > widgets can be used via the <persistentwidget> HTML element. The > <persistentwidget> HTML element takes a src attribute, like an iframe. In > order to make the <persistentwidget> survive a navigation, all of these > conditions must be met: 1. The navigation must be to a same-origin > document. 2. The <persistentwidget> element must have the same src and id > HTML attributes in both documents. 3. The <persistentwidget> element must > be attached to the new document before its first render. > > *Blink component* > Blink>HTML > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EHTML%22> > > *Web Feature ID* > Missing feature > > *Motivation* > Hard navigations of top-level documents result in the destruction of all > the child iframes of those documents. In cases of same-origin navigations, > there's high likelihood that at least some of those iframes would need to > be recreated on the new document. For iframes maintaining complex > client-side state (e.g. chat widgets, media players, collaborative editing > sessions, payment flows, embedded third-party apps), that results in loss > of state and user-visible performance implications. This significantly > disadvantages MPA architectures (that rely on hard same-origin navigations) > compared to SPA architectures, that can soft-navigate parts of the document > while leaving the iframes intact. That is particularly problematic for the > use-case of in-page agents, and runs a risk of causing web developers to > prefer SPAs due to that, despite potential performance and maintenance > costs related to that preference. > > *Initial public proposal* > https://github.com/WICG/persistent-iframes > > *Goals for experimentation* > None > > *Requires code in //chrome?* > False > > *Tracking bug* > https://issues.chromium.org/issues/537818859 > > *Estimated milestones* > > No milestones specified > > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/5155555348971520?gate=6206129112743936 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK6btwJsC353neof5Pau%2BDSAP0F85-oCTizBS8oipsg7PoNRhQ%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK6btwJsC353neof5Pau%2BDSAP0F85-oCTizBS8oipsg7PoNRhQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJSLZa0vc0BNPpegCHo25wCWT9m2LMcFY4DpzR0O6KRV2JMVtA%40mail.gmail.com.
