Re: [w3c/permissions] Introduce Browser Permissions for WebDriver BiDi (PR #425)

@marcoscaceres commented on this pull request.



> +          </p>
+          <p>
+            The <a>remote end steps</a> are:
+          </p>
+          <ol>
+            <li>Let |parameters| be the |parameters| argument, <a>converted to an IDL value</a> of
+            type {{PermissionSetParameters}}. If this throws an exception, return an [=invalid
+            argument=] [=error=].
+            </li>
+            <li>Let |rootDesc| be |parameters|.{{PermissionSetParameters/descriptor}}.
+            </li>
+            <li>If |parameters|.{{PermissionSetParameters/state}} is an inappropriate <a>permission
+            state</a> for any implementation-defined reason, return a [=invalid argument=] [=error=].
+              <p class="note">
+                For example, <a>user agents</a> that define the "midi" <a>powerful feature</a> as
+                "always on" may choose to reject a command to set the <a>permission state</a> to


```suggestion
                "always on" can choose to reject a command to set the <a>permission state</a> to
```

How would they do that though? It can only be set to "granted",   "denied",  or "prompt" ?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/pull/425#pullrequestreview-1740890635
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/permissions/pull/425/review/1740890635@github.com>