15:59:04 RRSAgent has joined #webdriver 15:59:09 logging to https://www.w3.org/2026/04/08-webdriver-irc 15:59:42 Meeting: April 2026 - Browser Testing and Tools WG Meeting 15:59:55 agenda: https://www.w3.org/wiki/WebDriver/2026-04-BiDi 15:59:59 Chair: David Burns 16:00:00 whimboo has joined #webdriver 16:00:06 scribe: David Burns 16:00:14 scribeNick: automatedtester 16:00:18 present+ 16:00:29 present+ 16:00:46 jimevans has joined #webdriver 16:01:02 present+ 16:03:53 jdescottes has joined #webdriver 16:03:59 present+ 16:04:11 rrsagent, make logs world-visible 16:04:12 present+ 16:04:18 rrsagent, make minutes 16:04:19 I have made the request to generate https://www.w3.org/2026/04/08-webdriver-minutes.html AutomatedTester 16:04:48 present+ 16:04:52 jgraham has joined #webdriver 16:05:03 present+ 16:05:14 RRSAgent: make minutes 16:05:15 I have made the request to generate https://www.w3.org/2026/04/08-webdriver-minutes.html jgraham 16:06:22 Topic: Reminder to review the PR for screencasting API 16:06:36 github: https://github.com/w3c/webdriver-bidi/pull/1069 16:07:35 q+ 16:07:42 jdescottes: This is a reminder to review the PR from sasha. Sasha is on PTO at the moment, please raise questions and we will answer to the best of our ability 16:07:50 ack next 16:08:14 q+ 16:08:40 orkon: I've been trying to prototype this and there web content API has been quite hard to use and there is nothing about stitching things so would need to be invited 16:09:01 ... but building it off web apis isn't doable 16:09:24 ... are there restrictions to what format needs to be output or is that up to the implementation 16:09:29 ack next 16:09:56 jgraham: I don't know what web rtc has but that format is likely the best 16:10:15 ... the other question has... 16:10:41 ... with web apis there is an idea that you are calling it from a IDL context which assumes javascript etc 16:10:50 ... we have a similar issue with the streams API 16:11:32 ... but when I suggested using something not using JS on streams the editor told me that wouldn't work as it would need a way of resolving promises 16:11:56 ... we would likely need to have a "specification realm" that is not a content realm and is something else 16:12:23 ... and it spec "fiction". It's like running script but not exactly like running a script 16:13:12 ... in Firefox this is easier and we know that doesn't mean much as in other browsers it could be a C++ type call 16:13:38 ... that's my best idea but if we don't do that then we are in a difficult position 16:13:59 q+ 16:14:11 ... it then becomes a very handwavy way doing "capture this and then output that with web rtc" 16:14:27 ... and it becomes unclear what realms this should run in 16:14:49 q? 16:14:51 ack next 16:15:37 orkon: thanks for the explaination. THis seems to work well for streams but I am not sure that works for screencast 16:16:24 q+ 16:16:27 ... but I might not have fully read those spec. The main thing is that we don't depend of the side effects of javascript execution other than the algorithm itself 16:16:29 ack next 16:17:43 jgraham: I need to look to see if this would work. parts of it works well but as a whole maybe not. THere might be a possiblity is that this is very complicated. We also have a way in the future that we can stream the browser not the file what we are currently thinging about 16:17:47 q? 16:18:10 topic: Should modified request cookies be present in the RequestData for network events 16:18:20 github: https://github.com/w3c/webdriver-bidi/issues/1110 16:19:22 jdescottes: cookies on modified requests... I realised when serialsing the network events that the current spec that we put the old cookie data into future events 16:19:54 ... this is because we are looping over the cookiejar and serialising what matches the network request 16:19:56 q+ 16:20:33 ... or should we returned the modified. If we do the modified that we can't return all the values as we can't see them all 16:20:53 ... or should we return the cookies in a different event later? 16:21:00 q? 16:21:04 ack next 16:21:58 orkon: I've commented on the issue... but in general from puppeteer that we don't have a use case for cookies on a network request. we have a separate cookie api 16:22:37 q+ 16:22:49 ... but I think we should the modified or a way to notify the user there is a change. I don't have a strong opinion on this either way 16:22:51 ack next 16:23:16 jdescottes: if there no other opinion then I will update the test accordingly 16:23:50 ... on the client side, do you have opinions on this @jimevans? 16:24:26 jimevans: I will need to check my use case that prompted me to log the bug 16:24:43 ... I can't remember what I was doing that caused the disconnect 16:24:47 q? 16:25:11 topic: emulation.setTextLayoutModeOverride 16:25:23 github: https://github.com/w3c/webdriver-bidi/pull/1072 16:26:07 orkon: there are a few PRs raised by Maksim. I wanted to check if there was anything that people wanted to do here? 16:28:32 whimboo: just checking is there a priority of PRs? 16:28:48 jgraham: I can see that Sasha has looked at this 16:29:07 jdescottes: it looks like some have been approved by sasha and we will ask her when back 16:30:02 RRSAgent: make minutes 16:30:03 I have made the request to generate https://www.w3.org/2026/04/08-webdriver-minutes.html jgraham