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

Specifying navigations affected by .well-known/change-password #29

Open
battre opened this issue Sep 16, 2020 · 0 comments
Open

Specifying navigations affected by .well-known/change-password #29

battre opened this issue Sep 16, 2020 · 0 comments

Comments

@battre
Copy link

battre commented Sep 16, 2020

We noticed that the current draft does not specify which navigations should be affected by .well-known/change-password. I can think of several possibilities:

  1. All navigations
  2. All navigations in the main frame
  3. Only navigations triggered by the browser (e.g. via a "Change password" button") - but not those triggered by a user-typed URL nor from links nor site-initiated navigations.

My intuition would go with 2 as this allows a website like https://passwords.google.com to just redirect to example.com/.well-known/change-password in the assumption that the user won't be greeted by a 404.

I can also see a reason for 3: In this case there would be less special casing for site-initiated navigations. Also browser extensions would probably have more control.

I don't see a lot of value in 1 (supporting the spec for iframes).

WDYT? @rmondello @hober

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

No branches or pull requests

1 participant