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

Endpoint for auto-replies of authorization prompt dialogs #1677

Closed
javifernandez opened this issue Aug 4, 2022 · 3 comments
Closed

Endpoint for auto-replies of authorization prompt dialogs #1677

javifernandez opened this issue Aug 4, 2022 · 3 comments

Comments

@javifernandez
Copy link

This new endpoint would have the purpose of handling the prompt dialog launched to ask the user for confirmation after a request of the registerProtocolHandler method. This is specified in the Custom Handler specification as follows:

A user agent could, for instance, prompt the user and offer the user the opportunity to add the site to a shortlist of handlers, or make the handlers their default, or cancel the request. User agents could also silently collect the information, providing it only when relevant to the user.

The request of a new endopoint has been suggested in a wpt related issue as a way to to avoid launching the prompt dialog, assuming some kind of auto-reply functionality.

Inspiration can be taken from:
https://w3c.github.io/permissions/#automation

In the case of the SetPermission extension command, it requires a PermissionDescriptor as an input argument. I've suggested to add a new descriptor for the Custom Handler spec, so that we could use this exception command. However, this proposal has been rejected clearly.

@whimboo
Copy link
Contributor

whimboo commented Aug 8, 2022

@AutomatedTester dupe of #385?

@javifernandez
Copy link
Author

I've filed an issue for the html spec to define a new extension command in the Custom Handlers section, so that we could handler automatically the prompt dialogs potentially launched by the registerProtocolHandler method.

We could close this issue if we finally implement such new WebDriver endpoint.

@javifernandez
Copy link
Author

We have implemented our new endpoont in the HTML spec so at least for that case, we don't need this issue anymore. Reopen if needed.

@whimboo whimboo closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2024
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

2 participants