-
Notifications
You must be signed in to change notification settings - Fork 35
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
JavaScript API general discussion #2
Comments
This is a bit of an attribute of the generality. I think that the simpler use cases are probably best served by something like privacycg/storage-access#55, which is simply a promise. My thinking here was to expressly expose what the current loading mode is, which matters more if this expands. For example, if we end up needing "network-isolated" and "fenced" as separate modes, you'd want to be able to distinguish them. And some of these might make sense to parameterize (for example, we might wish to expose the notion of being proxied in some way), so exposing a dictionary or interface rather than an enum makes this more extensible. If we're going to have an underlying primitive of "you are in this loading mode [therefore permissions policy is restricted in these ways, therefore you shouldn't necessarily record an impression, therefore ...]" in the spec, it seems natural to me to expose that to the platform too. |
Summarizing some discussion from #5 (comment) : We have a few paths we could go with a JS API for prerendering and other loading modes.
|
For now, the prerendering state API and other existing APIs should suffice. Related to #2.
For now, the prerendering state API and other existing APIs should suffice. Related to #2.
What is
document.loadingMode
? All we see is itstype
property, right?Should we use a promise instead of the sync getter + change event pattern?
The text was updated successfully, but these errors were encountered: