Re: [w3c/permissions] Add an optional `topLevelOrigin` parameter to the `permissions.setPermission` command (PR #468) from jalonthomas on 2025-09-01 (public-webapps-github@w3.org from September 2025)

From: jalonthomas <notifications@github.com>
Date: Mon, 01 Sep 2025 08:14:50 -0700
To: w3c/permissions <permissions@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/permissions/pull/468/c3242708166@github.com>

jalonthomas left a comment (w3c/permissions#468)

> Thanks - I'm still trying to wrap my head around how WebDriver-bidi implements all of this, there's quite a bit of indirection.

Right so the only change that we're realistically making is adding an optional topLevelOrigin to SetPermissionParameters [here](https://github.com/GoogleChromeLabs/chromium-bidi/blob/0a6af6579fd89754d8e7e397dfb44d905e40e1df/src/protocol/generated/webdriver-bidi-permissions.ts#L43). That's the input to the link that you sent. We'll then parse that value as well and send it using Broser.setPermission.

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

Message ID: <w3c/permissions/pull/468/c3242708166@github.com>

Received on Monday, 1 September 2025 15:14:54 UTC