-
Notifications
You must be signed in to change notification settings - Fork 348
Realm for "package data" #400
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
Comments
Yeah. As I mentioned elsewhere, IDL really needs to start to define how an object is allocated as an abstract operation and then we should force everyone to go through that whenever they allocate an object of sorts. And then perhaps some convenient functions around that. For instance: Allocate(realm, interfaceToAllocate); AllocateFromThis(this, interfaceToAllocate); AllocateFromCurrent(interfaceToAllocate). |
I think we should stick with the plan in whatwg/webidl#135 as that will be least disruptive. It will only require people to specify the realm when they're doing something asynchronous (i.e. not the sync consequence of a method or constructor call). In that case maybe having a term like "allocate" is good, and then we'd say "allocate an object x using interface I in realm r". Otherwise people can say "allocate an object x using interface I" or any of their current imprecise phrasings. |
If that's the plan I guess I don't technically need to change anything here, since we do have a this object. |
https://fetch.spec.whatwg.org/#body-mixin
… creates a
Blob
without defining its global object.The text was updated successfully, but these errors were encountered: