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

Let specs define their own default mediation requirement #258

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Aug 23, 2024

Closes #256

The following tasks have been completed:

  • Modified Web platform tests (link to pull request)

Implementation commitment:


Preview | Diff

index.bs Show resolved Hide resolved
</blockquote>
</div>

Additionally, a specification can add its own set of restriction around what mediations are allowed to be passed into the API.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should probably be more explicit about the internal methods.

index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
Copy link
Member

@nsatragno nsatragno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know how I missed this -- sorry.

I think we don't actually need to do this and have commented on the issue, but left some comments in case we still want to pursue it.

@@ -988,6 +992,11 @@ spec:css-syntax-3;
1. If |interfaces| is [=set/empty=], then return[=a promise rejected with=]
a "{{NotSupportedError}}" {{DOMException}}.

1. If |options|.{{CredentialRequestOptions/mediation}} was not passed,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I believe

Suggested change
1. If |options|.{{CredentialRequestOptions/mediation}} was not passed,
1. If |options|.{{CredentialRequestOptions/mediation}} is `null` or `undefined`,

might be more accurate.

@@ -1194,6 +1203,11 @@ spec:css-syntax-3;

1. Let |interfaces| be the [=set=] of |options|' <a>relevant credential interface objects</a>.

1. If |options|.{{CredentialRequestOptions/mediation}} was not passed,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(same)

@@ -504,6 +504,10 @@ spec:css-syntax-3;
internal slot named <dfn for="Credential" attribute>\[[origin]]</dfn>, which stores the [=origin=]
for which the {{Credential}} may be [=effective=].

Credential interfaces can define a <dfn for="Credential" export>default get mediation</dfn> and
<dfn for="Credential" export>default create mediation</dfn> as an {{CredentialMediationRequirement}} enum value.
Together, they establish the default [[#mediation-requirements]] for when none are supplied by the developer.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens when two credential types define two different mediation types?

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

Successfully merging this pull request may close these issues.

Should mediation be defaulted at all?
2 participants