-
Notifications
You must be signed in to change notification settings - Fork 9
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
Comments
Spec is outdated compared to latest explainer. Note: quote is from https://wicg.github.io/pending-beacon/#pendingbeacon-interface |
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. |
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. |
Clarification and subsequent works have been addressed as |
Early in the document you say it's scoped to a document, but then elsewhere you do
The text was updated successfully, but these errors were encountered: