-
Notifications
You must be signed in to change notification settings - Fork 166
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
Should the "authentication" attribute on Navigator be [SameObject]? #249
Comments
It seems to me that |
Until it is specified what this returns, it can be a source of interop issues. We need to specify this for the Implementer's Draft. |
From discussion on the call, it sounds like we should do this. |
@bzbarsky -- might you have a ptr to example text that addresses: "the return value should depend only on the "this" value, and should be associated to the same global as the "this" value." ? |
Addresses in what sense? The obvious way to do that is to have it stored in a slot of "this", create when needed, when creating use the relevant global of "this". |
I think this is obviated by #384, which moves things to |
And in general, should it have some sort of processing model defined? Right now nothing defines what this attribute actually returns. Does the returned value depend on the "this" value, or on the Realm of the attribute getter, or something else?
Presumably this should be [SameObject] hence and the return value should depend only on the "this" value, and should be associated to the same global as the "this" value.
The text was updated successfully, but these errors were encountered: