15:49:03 RRSAgent has joined #webdriver 15:49:08 logging to https://www.w3.org/2025/10/08-webdriver-irc 15:49:09 Zakim has joined #webdriver 15:55:00 Meeting: WebDriver Oct 2025 15:55:07 chair: David Burns 15:56:02 Agenda: https://www.w3.org/wiki/WebDriver/2025-10-BiDi 15:56:09 scribe: David Burns 15:56:16 scribenick: AutomatedTester 15:56:54 rrsagent, set logs world-visible| 15:56:59 rrsagent, set logs world-visible 15:57:03 shs has joined #webdriver 15:57:12 rrsagent, create minutes 15:57:14 I have made the request to generate https://www.w3.org/2025/10/08-webdriver-minutes.html AutomatedTester 15:57:29 lauromoura has joined #webdriver 15:57:38 present+ 15:58:12 present+ 15:58:39 jdescottes has joined #webdriver 16:00:27 present+ 16:00:32 jimevans has joined #webdriver 16:00:47 present+ 16:00:47 present+ 16:02:06 present+ 16:02:34 jgraham has joined #webdriver 16:02:42 present+ 16:02:47 RRSAgent: make minutes 16:02:48 I have made the request to generate https://www.w3.org/2025/10/08-webdriver-minutes.html jgraham 16:03:40 Agenda: https://www.w3.org/wiki/WebDriver/2025-10-BiDi 16:03:47 topic: Data collection for cached reponses 16:03:58 github: https://github.com/w3c/webdriver-bidi/issues/985 16:04:54 jdescottes: data collection for cached responses. the current spec is has that we get a stream from fetch but we don't have anything coming from the cached version 16:05:05 q+ 16:05:27 ... my feeling is that we should consistently return data even if it doesnt go over the network 16:05:42 ... or should we have it handle the cached version consistently? 16:05:44 ack next 16:05:49 present+ 16:06:06 q+ 16:06:10 sadym: could we start with WPT tests ? to verify that we have the same behaviour 16:06:12 ack next 16:06:22 blaze_apple has joined #webdriver 16:06:29 jdescottes: we can, we have mozilla specific wpt test that does that 16:06:31 present+ 16:06:53 ... in chromium it does it for all where firefox doesnt do that for css or images 16:07:09 ... we can have the spec to have it say to return a response text 16:07:10 q+ 16:07:13 ack next 16:07:50 jgraham: if the spec doesn't say that we should have the right response... i'm not sure what gecko is doing here 16:08:35 ... we need to make it consistent as authors don't expect to have inconsistency here 16:08:40 q? 16:09:02 topic: Data collection for data scheme 16:09:18 github: https://github.com/w3c/webdriver-bidi/issues/986 16:09:41 jdescottes: this is the same topic as the previous... we don't have a stream we can clone 16:10:23 q+ 16:10:24 ... we've updated Firefox to be similar to chrome. Are people happy for me to return a response body for data urls? 16:10:27 ack next 16:10:32 mradbourne has joined #webdriver 16:10:32 q+ 16:11:20 blaze_apple: In general this is fine. What do we do if the page is navigated away... e.g. if the process dies or ... 16:11:24 ack next 16:11:53 jdescottes: we don't clean collected data. We currently do this with a queue 16:12:14 ... and we can handle the situation when collectors are cleaned up 16:12:24 ... but we don't do anything for navigation 16:12:51 sadym: I wonder what selenium thinks about this? 16:12:54 q+ 16:13:16 ack next 16:13:42 jimevans: how does selenium feel about cached responses or when the navigation has happened? 16:13:49 sadym: about data schema 16:14:20 jimevans: I am of the opinion that we are doing network interception or of data 16:14:43 ... whether it comes over any scheme we should be able to retrieve that data 16:14:53 ... and I expect selenium users to think the same 16:14:56 q? 16:15:42 topic: Autofill trigger 16:15:57 github: https://github.com/w3c/webdriver-bidi/pull/706 16:16:17 q+ 16:16:21 sadym: this PR has been sitting there and we need to have other vendors review so that we can unblock and get this landed 16:16:25 ack next 16:17:24 jgraham: I havent had time to look but I think the last time this was discussed and it needed changes but there doesn't appear to have been updated. I will need to re-read the PR 16:17:28 q? 16:17:55 topic: Pending Fetch spec changes 16:18:10 github: https://github.com/whatwg/fetch/pull/1540 16:18:34 q+ 16:18:52 sadym: we have a couple of pending PR changes. I wonder if we can get these ublocked and landed? 16:18:59 s/ublocked/unblocked 16:19:04 q+ 16:19:08 ... how can we make prgress on this? 16:19:10 ack next 16:19:10 github: https://github.com/w3c/webdriver-bidi/issues/722 16:19:38 jgraham: I have linked the original issue that is blocked on fetch changes 16:20:12 ... I think we reuse events and we can't tell the order properly 16:20:35 ... when it was reviewed Anne he wasn't happy and we have made changes 16:21:14 ... I am not sure if the new model is sufficient here and we need to make sure that it is before we can get it updated/landed 16:21:17 q? 16:21:19 ack next 16:22:04 jdescottes: nothing much to add. I will try settle on what we wanted and I will take jgraham's PR and update to get it landed 16:22:06 q? 16:22:23 topic: Preparing horizontal reviews on the way to Candidate Recommendation 16:22:33 github: https://github.com/w3c/webdriver-bidi/issues/906 16:22:55 tidoust: A meta issue has been raised to get this to CR 16:23:09 ... I have started to get the a11y feedback 16:23:34 ... for privacy and security, we don't have that section yet and we should get that added 16:23:53 ... the classic webdriver spec has it and we might be able to copy and paste it 16:23:56 q+ 16:24:06 ... so how should we proceed? 16:24:09 ack next 16:24:36 jgraham: for privacy and security, we use the classic spec as a starting point but we need to have it updated 16:25:41 ... the other thing from before we didn't have a11y consideration but we might have i18n issues. Is that going block review? 16:26:09 tidoust: I will ask the i18n group and we need to know how to handle error messages for example 16:26:29 lauromoura has joined #webdriver 16:26:52 ... I don't think we should block on this. I think should go for review and just highlight it and it's not a priority 16:27:36 jgraham: I think in practise that people are hard coding error messages in english but if people arent then that would be great 16:28:13 ... the assumption I have is no one is doing it makes how we handle it simpler 16:28:31 tidoust: I will draft the initial PR for the privacy and sec 16:28:43 ... and I will get moving on the other reviews in the meantime 16:28:44 q? 16:29:21 topic: WPT for extra headers 16:30:02 sadym: this is an area that i will start working on this after I finish the offline work unless someone else wants to pick this up? 16:30:06 q+ 16:30:11 ack next 16:30:37 jdescottes: sounds good from our side. it's not something we will be working on any time soon? 16:30:54 sadym: do we want just custom headers or do we want standard headers 16:31:19 jgraham: I think we should do standard headers too incase there are interop issues there that we might be unaware of 16:31:27 q? 16:32:32 q+ 16:33:39 q+ 16:33:44 ack next 16:34:54 ack next 16:39:12 RRSAgent: make minutes 16:39:13 I have made the request to generate https://www.w3.org/2025/10/08-webdriver-minutes.html jgraham 16:39:19 Zakim, bye 16:39:19 leaving. As of this point the attendees have been AutomatedTester, shs, lauromoura, jimevans, jdescottes, sadym, jgraham, tidoust, blaze_apple 16:39:19 Zakim has left #webdriver 16:39:43 RRSAgent: bye 16:39:43 I see no action items