You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While adding support for the automation over WebDriver BiDi, I have noticed that Set a permission specifies that the permissions should be changed for only currently existing browsing contexts (unless I am misinterpreting?):
It does sound like if a new browsing context (and IIUC a new context would have a new environment settings object) with a previously configured origin gets created, it should not inherit the previously set permissions. I think that current implementation in Chrome does propagate previously set permissions to new contexts and I think this is what would be expected because the origin (and not a context) is an input for the method.
While adding support for the automation over WebDriver BiDi, I have noticed that Set a permission specifies that the permissions should be changed for only currently existing browsing contexts (unless I am misinterpreting?):
It does sound like if a new browsing context (and IIUC a new context would have a new environment settings object) with a previously configured origin gets created, it should not inherit the previously set permissions. I think that current implementation in Chrome does propagate previously set permissions to new contexts and I think this is what would be expected because the origin (and not a context) is an input for the method.
Test case:
The text was updated successfully, but these errors were encountered: