[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

On Wed, 8 Nov 2023 at 21:07, Fergal Daly wrote: > > > On Thu, 26 Oct 2023 at 01:11, Kevin D. > wrote: > >> Understood. >> >> >>1. *Is there any action required from us until general rollout (when >>`unload` isn’t fired anymore)?* >> >> No. > >> >>1. *Is there a list of this restricte

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

On Thu, 26 Oct 2023 at 01:11, Kevin D. wrote: > Understood. > > >1. *Is there any action required from us until general rollout (when >`unload` isn’t fired anymore)?* > > No. > >1. *Is there a list of this restricted set domains with which you’re >experimenting?* Want to know if

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

Understood. 1. *Is there any action required from us until general rollout (when `unload` isn’t fired anymore)?* 2. *Is there a list of this restricted set domains with which you’re experimenting?* Want to know if ours are included 3. *We should have `pagehide` replacement by

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

On Wed, 25 Oct 2023 at 05:28, Kevin D. wrote: > Thanks F > > I see origin trial [1] starts soon with 119 and I need clarification: > That origin trial is a little confusing. It ended up not being implemented in 119 and may not even make it into 120. However we not roll this out generally for any

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

Thanks F I see origin trial [1] starts soon with 119 and I need clarification: 1. *Does this mean starting Chrome 119, `unload` won't be fired? * 2. The Permissions Policy alternative does not work with sourceless iframes (iframes using `srcdoc`). You filed a bug [2] earlier for that after I ra

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

*Does the Permissions-Policy: unload API not support sourceless subframes?* (i.e. iframes without *src* attributes and with content set inline in *srcdoc*) My team uses sourceless iframes, and hooks to the *unload* event for cleaning up resou

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

Thanks Kevin. Replies in-line. On Wed, 11 Oct 2023 at 09:30, Kevin D. wrote: > *Does the Permissions-Policy: unload API > not support sourceless > subframes?* (i.e. iframes without *src* attributes and with content set > inline in *srcdoc*) > >

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

On Tue, Apr 18, 2023 at 7:34 PM Fergal Daly wrote: > [+iclelland] > > On Tue, 18 Apr 2023 at 23:19, Nic Jansma wrote: > >> Hi Kenji, >> >> Will there be a way to detect whether or not unload will fire from JS? >> > > I don't believe there is a way to query the policies that currently apply > to

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

[+iclelland] On Tue, 18 Apr 2023 at 23:19, Nic Jansma wrote: > Hi Kenji, > > Will there be a way to detect whether or not unload will fire from JS? > I don't believe there is a way to query the policies that currently apply to a document. Ian, is there? Should there be? You could attempt to a

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

Hi Kenji, Will there be a way to detect whether or not unload will fire from JS? We (Akamai) have some security products that may hook into unload, *only* if they detect that *another* script has hooked into unload. When this happens, we also shift some "cleanup" work to that unload handler th

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

In light of this feedback, we are landing a metric to understand how often subframe unload handlers run without main frame navigation. We'll use the data to adjust our plans accordingly. Since it takes time to get & analyze the data, *we are pushing the proposed behavior change to M115*. *Adju

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

[+sm...@mozilla.com] I'm relaying a piece of feedback from Mozilla in this github issue . It's possible that pages are depending on `unload` handlers in subframes for functionality even without any main frame navi

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

At my company, we've been using the original trial since it has launched and found improved metrics. We've tried pushing one tracking company to remove the unload listener from multiple contact points with no success, leaving us only with the origin trial as option to enable BFCache. We found n