Skip to content

Clarify UI formulation flexibility and cooldowns in spec algorithms #840

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.

Sign up for GitHub

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

Merged
npm1 merged 1 commit into from
Jul 23, 2026
Merged

Clarify UI formulation flexibility and cooldowns in spec algorithms #840

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 19 additions & 2 deletions spec/index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -961,6 +961,16 @@ the exception immediately.
1. Return (failure, false).
1. Let |allAccounts| be an empty [=list=].
1. Build UI by adding the following for each (|providerOrigin|, |value|) in |providerMap|:

<div class="note">
Note: The visual formulation, placement, and timing of the UI described in these steps (such
as a modal dialog, bubble, bottom sheet, or a quiet URL bar indicator) are

@TallTed TallTed Jul 24, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Either an extra article --

Suggested change
as a modal dialog, bubble, bottom sheet, or a quiet URL bar indicator) are
as a modal dialog, bubble, bottom sheet, or quiet URL bar indicator) are

@TallTed TallTed Jul 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Or a few missing articles --

Suggested change
as a modal dialog, bubble, bottom sheet, or a quiet URL bar indicator) are
as a modal dialog, a bubble, a bottom sheet, or a quiet URL bar indicator) are

implementation-defined. The user agent MAY defer presenting the account options until the
user interacts with a passive affordance, and MAY suppress or dismiss the UI (returning
(failure, false)) at any point based on user preferences, active page state, or cooldown
heuristics (such as exponential back-off after prior dismissals).
</div>

1. If |value| is "logged-out", the user agent adds one of the following:
* Nothing: no UI is shown regarding this [=IDP=].
* Return (failure, false).
Expand Down Expand Up @@ -1645,8 +1655,15 @@ and a |globalObject|, run the following steps. This returns a boolean.

Note: Omitted is different from an explicitly present empty list.
1. Prompt the user to gather explicit intent to create an account. The user agent MAY use the
{{IdentityProviderBranding}} to inform the style choices of its UI. Additionally, if the user agent
<dfn>supports showing a permission prompt</dfn>:
{{IdentityProviderBranding}} to inform the style choices of its UI.

<div class="note">
Note: The user agent MAY combine gathering explicit intent to create an account (and
displaying the privacy policy and terms of service) with the account selection UI itself, or
present it as a distinct step.
</div>

Additionally, if the user agent <dfn>supports showing a permission prompt</dfn>:

Note: Identity providers should support showing their own permission prompt using
{{IdentityAssertionResponse/continue_on}} when the `disclosure_shown_for` parameter
Expand Down
Loading