Closed thiagowfx closed 5 months ago
The Browser Testing and Tools Working Group just discussed Permission extensions
.
The Browser Testing and Tools Working Group just discussed
Permission extensions
. The full IRC log of that discussion
And there was one more comment from @jgraham that actually sneaked into the logs for https://github.com/w3c/webdriver-bidi/issues/287#issuecomment-1802375543:
(don't want to extend this topic further, but I always assumed BiDi would move to an event-based model for permissions i.e. you'd get a permissions.Request event with some information)
The recommendation was added (https://github.com/w3c/webdriver-bidi/pull/605), and the umbrella issue in the permissions repo was closed (https://github.com/w3c/permissions/issues/424), therefore this can be closed.
I'll just note that there's one missing AI from https://github.com/w3c/permissions/issues/424:
TODO: Add
user context
toSetPermissionParameters
@OrKoN you may want to open a separate bug/FR for that, if still relevant
Permissions spec umbrella issue: https://github.com/w3c/permissions/issues/424
"Interacting with Permissions for Powerful Features"
The WebDriver BiDi spec spec should support interaction with browser permissions as an extension module. These permissions represent a user's choice to allow or deny access to "powerful features" of the platform. For developers, the specification standardizes an API to query the permission state of a powerful feature, and be notified if a permission to use a powerful feature changes state.
The Permissions spec already supports WebDriver classic. This bug is about making it support WebDriver BiDi as well.
References:
Soft references: