Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scoping confusion #64

Closed
annevk opened this issue Feb 8, 2023 · 4 comments
Closed

Scoping confusion #64

annevk opened this issue Feb 8, 2023 · 4 comments
Labels
spec Issue with spec

Comments

@annevk
Copy link

annevk commented Feb 8, 2023

Early in the document you say it's scoped to a document, but then elsewhere you do

Insert beacon into the user agent’s pending beacon set.

@mingyc mingyc added the spec Issue with spec label Feb 14, 2023
@mingyc
Copy link
Collaborator

mingyc commented Feb 14, 2023

Spec is outdated compared to latest explainer.

Note: quote is from https://wicg.github.io/pending-beacon/#pendingbeacon-interface

@clelland
Copy link
Collaborator

clelland commented Mar 8, 2023

I originally wrote that as I expected that, while the beacon data is associated with a specific document, it needs to be owned by the UA so that it can continue to exist (and be sent) when the document is destroyed. So the conceptual model is that the UA has set of beacons, and knows what documents each is associated with, and decides when to send them.

@annevk
Copy link
Author

annevk commented Mar 8, 2023

How can it know about the document if the document is destroyed? That doesn't quite add up. You'd need to associate a bunch of state explicitly with it.

@mingyc
Copy link
Collaborator

mingyc commented Nov 13, 2023

Clarification and subsequent works have been addressed as fetchLater() API in whatwg/fetch#1647 and whatwg/fetch#1715.

@mingyc mingyc closed this as completed Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec Issue with spec
Projects
None yet
Development

No branches or pull requests

3 participants