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

Jump to bottom

Because browser extensions can leverage page content, should that constrain support for generic clients? #2

Open

darrelmiller opened this issue Nov 3, 2024 · 0 comments

Collaborator

darrelmiller commented Nov 3, 2024

From SECDIR Review https://datatracker.ietf.org/doc/review-ietf-httpapi-authentication-link-01-secdir-early-schwartz-2024-06-28/

It imagines
a world where the "login state" of users on websites is presented explicitly in
the browser chrome, rather than within the page content, and provides some
affordances to that effect. However, it does not mention any review from the
W3C or related web groups to confirm that this is something desired by the web
community.

There definitely are some members of the web community that wishes it were easier to find the login button on a web page https://ux.stackexchange.com/questions/142394/what-is-a-better-way-to-present-sign-up-login-form

darrelmiller added this to HttpApi Active Issues

darrelmiller moved this to In Discussion in HttpApi Active Issues

darrelmiller moved this from In Discussion to Seeking Feedback in HttpApi Active Issues

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