You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some discussion about whether a pending (or deferred) fetchLater request should be sent if a prerendered page is cancelled, i.e. not actually visited by users.
Do developers expect such requests be made or not?
The text was updated successfully, but these errors were encountered:
So chatted with a few RUM providers (including @nicjansma above!) and general consensus seemed to be that they likely wouldn't fire beacons on non-activated pages anyway so don't need the API to support this.
However, one did raise the point that, while they didn't see a use case for it right now, other JavaScript APIs work on prerendered pages (though some user-facing ones are delayed until activation) so there should be a good reason why this one (which is specifically there to be reliable), wouldn't in case anyone did want to use it (e.g. to more easily track the number of prerendered pages that were not activated). Which I think is a fair point.
There are some discussion about whether a pending (or deferred) fetchLater request should be sent if a prerendered page is cancelled, i.e. not actually visited by users.
Do developers expect such requests be made or not?
The text was updated successfully, but these errors were encountered: