This rolled out to 100% long ago. It is enabled by default in M105 onwards. Just having a DedicatedWorker does not block BFCache but just like a frame in the page, the worker may still do things that block BFCache.
I just realized that the Chrome-status was never updated, I have marked is as on by default now, F On Fri, 26 May 2023 at 03:51, Aaron Grogg <agr...@estee.com> wrote: > Initial message dated May 7, 2022, but no updates or notes since... > > Curious as to the status of this; still a blocker, or resolved? > > Thanks! > Atg > > > On Monday, March 7, 2022 at 7:28:13 PM UTC-8 Fergal Daly wrote: > >> FYI, we are about to start a finch experiment to enable BFCaching of >> pages with Dedicated Workers. This is not an I2S because there's no new API >> or new capabilities. It's just another existing feature that used to block >> BFCache but won't anymore. Also, WebKit and Mozilla already do this. >> >> That said, it was a fairly large piece of work (https://crbug.com/1146955) >> and up until now, creating a DW would keep you out of BFCache so this is a >> visible change. As a result we are giving a heads-up. Chrome-status link is >> here <https://chromestatus.com/guide/edit/5720508250193920>. >> >> Devs can check what, if anything, is blocking their site from being >> BFCached by looking in Devtools under Application -> Back/forward cache. If >> only the only blocking reason is DedicatedWorkerOrWorklet, their page may >> start being BFCached with this change. We estimate that about 2% of Android >> and < 1% of Desktop history navigations are blocked by this reason alone >> and could start to use BFCache, >> >> F >> >> -- 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAozHLmuMFGVioOOCwbLxG4DundvDuGRe-h%2Bubf96uqr5%3DK%3DxA%40mail.gmail.com.
