Re: [w3ctag/design-reviews] Early Design Review: Pending Beacon API (Issue #776)

Hi, @maxpassion and I reviewed this during our F2F and we have a few questions:

About the use of Get/PostPendingBeacon, why not using the method in a dictionary instead of having two instances? How about ensuring that a PostPB isn't sent twice (like if there is a crash).
Issues about crash recovery, should it be done after a network and/or location change, as it can have privacy implications? after a time limit? 
Do having a pending beacon registered impact how bfcache work?

What is the point of forcing a PendingBeacon to be sent, if it is supposed to be sent at the end of the interaction, why not using fetch or a normal beacon in that case?

Why existing mechanism is not reliable and how this new proposed mechnisam solve the not reliable issue? Should the HTML unload event be fixed instead? Could this be solved at the Page Lifecycle level instead of having a new specification?

Thanks,

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/776#issuecomment-1420484493
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/776/1420484493@github.com>