– DRAFT –
WebDriver-BiDi

RRSAgent: make logs public

RRSAgent: make minutes

AutomatedTester: tidoust will be the Team Contact.

AutomatedTester: I'm going to send an email about the FPWD this week

tidoust: Hello everyone! I've been staff contact for other WGs in the media space, and I've been developing many tools for working with specs. I'm a big user of Puppeteer and other frameworks.

Supporting await in Execute Script

github: w3c/webdriver#1436

jugglinmike: I filed this issue 5 years ago, and let it drop, but I'd like to pick it back up to gauge interest. Should `await` be supported in `execute script` in WebDriver classic, or indeed `execute async script` where it means whether the script is considered async. There are already wpt that assume this. Chrome and Safari pass, but Firefox has

an open bug.

jugglinmike: Not sure what the status of Firefox is, or is intended to be. Not sure what needs to change here. Either update classic to match the implementations of Chrome and Safari or update wpt to remove the tests if we think the behaviour is wrong.

jgraham: Since it's purely a superset, it makes sense to me to include it.
… I don't know when we'll get to it in Firefox
… but that seems reasonable in any case.

jugglinmike: There's a potential problem using promises to model async operations because we don't have an environment settings object. I don't know if I can do this cleanly. THat's something that will require further discussion. But I'm happy to worry about that later.

jugglinmike: seems like I can get to work on updating the spec.

Input events dispatch to top-level frame

github: w3c/webdriver-bidi#795

sadym: BiDi allows sending input events to any context including iframes. However if the user wants to test that there is nothing interrupting that click they have to dispatch to the top-level target on the coordinates of the button and check if the event bubbled down through the layers. I don't think classic has the problem because we can only

target top level traversables. Do we want to adjust the specification so that all events go via all the browsing contexts?

jgraham: I don't know what the answer is, it's a real problem. I think we're doing something similar to what you suggest to dispatch the event through iframes. We would need to check what's possible.
… We should specify you're not directly targeting the iframe, and probably we're not doing that correctly at the moment.

sadym: You're saying it's a good idea to dispatch from th tlbc?

jgraham: Yes

sadym: The specification currently says that you have to make it equivalent to performing the events on the given context, but we want to change to the top-level context, right?

jgraham: Yes, I think so

sadym: OK, I'll do that

Web Extensions

github: https://github.com/w3c/webdriver-bidi/pull/778/

github: https://github.com/w3c/webdriver-bidi/issue/778/

jgraham: We have a PR from a contributor. If you're interested in web extensions, please review this PR

AutomatedTester: I'll take a look