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

Various attributes of ScopedCredentialInfo should probably be [SameObject] #285

Closed
bzbarsky opened this issue Nov 4, 2016 · 10 comments
Closed

Comments

@bzbarsky
Copy link

bzbarsky commented Nov 4, 2016

I expect the value they return never changes, right?

@equalsJeffH
Copy link
Contributor

perhaps -- tho, "never changes" relative to what? I guess I'm uncertain wrt all the implications of [SameObject].

@equalsJeffH equalsJeffH added this to the WD-04 milestone Nov 7, 2016
@bzbarsky
Copy link
Author

bzbarsky commented Nov 7, 2016

tho, "never changes" relative to what?

[SameObject] means that if the attribute getter or method thus annotated is invoked twice with the same "this" value, the return value will be the same, no matter what other script executes between the two invocations, whether the event loop spins between the two invocations, etc.

@selfissued
Copy link
Contributor

This issue proposes specific semantic refinements affecting interop. Therefore, I believe we should decide this before the Implementer's Draft.

@AngeloKai
Copy link
Contributor

The issue doesn't impact the actual behavior but rather just add description to categorize the behavior. I removed the implementation-priority flag because it doesn't impact our codebase.

@bzbarsky
Copy link
Author

bzbarsky commented Apr 5, 2017

It would impact Gecko's codebase, fwiw.

@selfissued
Copy link
Contributor

On the call, people agreed with doing this. The exact list of attributes affected needs to be specified.

@equalsJeffH
Copy link
Contributor

@bzbarsky which attrs were you thinking are [SameObject] ?

@bzbarsky
Copy link
Author

bzbarsky commented Apr 5, 2017

"all of them" in this case, no? I only see two in the spec at this point, and I expect they are both [SameObject], but I haven't read the currently updated spec carefully to check whether this is true.

@equalsJeffH equalsJeffH self-assigned this Apr 5, 2017
@AngeloKai AngeloKai modified the milestones: WD-06, WD-05 May 3, 2017
@jyasskin
Copy link
Member

Ok, this wasn't entirely fixed by the Credential Manager merge. The remaining attributes that should be [SameObject] are:

interface PublicKeyCredential : Credential {
    readonly attribute ArrayBuffer           rawId;
    readonly attribute AuthenticatorResponse response;
    readonly attribute AuthenticationExtensions clientExtensionResults;
};

[SecureContext]
interface AuthenticatorResponse {
    readonly attribute ArrayBuffer clientDataJSON;
};

[SecureContext]
interface AuthenticatorAttestationResponse : AuthenticatorResponse {
    readonly attribute ArrayBuffer attestationObject;
};

[SecureContext]
interface AuthenticatorAssertionResponse : AuthenticatorResponse {
    readonly attribute ArrayBuffer      authenticatorData;
    readonly attribute ArrayBuffer      signature;
};

@equalsJeffH
Copy link
Contributor

[SameObject] definition is here.

So it seems @jyasskin is asserting that all the readonly interface attrs in our collected WebAuthn IDL ought to be [SameObject]. Looks reasonable to me. I will effect the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants