15:51:32 <RRSAgent> RRSAgent has joined #webdriver
15:51:36 <RRSAgent> logging to https://www.w3.org/2023/08/09-webdriver-irc
15:51:47 <Zakim> Zakim has joined #webdriver
15:54:08 <AutomatedTester> meeting: WebDriver WG August 2023
15:54:20 <AutomatedTester> chair: David Burns
15:54:30 <AutomatedTester> Scribe: David Burns
15:54:38 <AutomatedTester> ScribeNick: AutomatedTester
15:54:44 <AutomatedTester> Agenda: https://www.w3.org/wiki/WebDriver/2023-08-BiDi
15:54:54 <AutomatedTester> present+
15:55:30 <AutomatedTester> rrsagent, make logs world-visible
15:58:31 <JimEvans> present+
16:00:12 <orkon> present+
16:01:10 <mathiasbynens> present+
16:01:24 <simonstewart> simonstewart has joined #webdriver
16:02:22 <jgraham> present+
16:03:01 <jdescottes> present+
16:03:07 <sasha> present+
16:03:10 <whimboo> present+
16:03:17 <lightning00blade> present+
16:03:36 <simonstewart> present+
16:04:04 <jrandolf> present+
16:04:05 <gsnedders> present+
16:04:46 <AutomatedTester> topic: TPAC
16:06:19 <cb> present+
16:07:21 <AutomatedTester> Automatedtester: I have made sure that we have session space during TPAC on the Thursday and Friday. I can't be there unfortunately
16:07:37 <orkon> q+
16:07:56 <AutomatedTester> jgraham: I think that we need to work out who is going to be there in person.
16:08:06 <AutomatedTester> ... we should probably set the agenda ahead of time
16:08:26 <AutomatedTester> ack next
16:08:56 <JimEvans> q+
16:08:58 <AutomatedTester> orkon: I will be there in person with Maksim and a couple other googlers.
16:09:07 <AutomatedTester> ack next
16:09:23 <AutomatedTester> Jim Evans: I will be there as a remote attendee
16:09:35 <jgraham> RRSAgent: make logs
16:09:35 <RRSAgent> I'm logging. I don't understand 'make logs', jgraham.  Try /msg RRSAgent help
16:10:45 <jgraham> RRSAgent: make minutes
16:10:46 <RRSAgent> I have made the request to generate https://www.w3.org/2023/08/09-webdriver-minutes.html jgraham
16:11:01 <AutomatedTester> action: David - Make sure agenda is ready ahead of time and organsie the remote participation links
16:11:17 <AutomatedTester> topic: Network request interception update
16:11:27 <AutomatedTester> github: https://github.com/w3c/webdriver-bidi/pull/429
16:11:58 <AutomatedTester> jgraham: this is mostly an update. I think the initial PR of this is ready to land
16:12:37 <AutomatedTester> ... we know the URL matching is not 100% done yet but it's heading in the right direction
16:12:51 <AutomatedTester> ... my recommendation is we land the current PR and then any issues get followed up in a future PR
16:12:51 <JimEvans> q+
16:12:53 <orkon> q+
16:12:56 <AutomatedTester> ack next
16:13:40 <AutomatedTester> Jim Evans: I am happy with this process so we get as much landed now and future URL matching in a future PR
16:13:43 <jgraham> q+
16:13:54 <AutomatedTester> ack next
16:14:24 <jdescottes> q+
16:14:48 <AutomatedTester> orkon: on our side Diego is working on this but he is OOO this week. We were hoping to do some prototyping but it is looking good and we can get it landed sooner
16:14:51 <AutomatedTester> ack next
16:15:53 <AutomatedTester> jgraham: regarding the network response bodies I think that would be a good topic for TPAC. I didn't think it was a priority at the beginning but we can definitely follow up
16:15:56 <AutomatedTester> ack next
16:16:36 <AutomatedTester> jdescottes: Diego looked at this before going on PTO and he seemed happy with getting this landed as is
16:16:42 <AutomatedTester> q?
16:16:44 <orkon> Diego -> Thiago
16:16:48 <whimboo> s/Diego/Thiago
16:17:45 <AutomatedTester> topic: Add browsingContext parameter to script.addPreloadScript
16:18:03 <AutomatedTester> github: https://github.com/w3c/webdriver-bidi/issues/373
16:18:09 <orkon> q+
16:18:14 <AutomatedTester> ack next
16:19:20 <jgraham> q+
16:19:35 <AutomatedTester> orkon: we are working on doing preload script. We are doing an implementation in this puppeteer. When working on this we found we couldn't implement this without the browsing context
16:19:38 <AutomatedTester> ack next
16:20:43 <orkon> q+
16:20:48 <AutomatedTester> jgraham: I think that should be pretty straight forward to specify. I would also like to understand the use case better
16:20:52 <AutomatedTester> ack next
16:21:29 <whimboo> q+
16:21:36 <jrandolf> q+
16:21:43 <AutomatedTester> orkon: the use case is to support the puppeteer API. It allows people to have some isolation for preload scripts
16:21:48 <AutomatedTester> ack next
16:22:23 <jgraham> q+
16:22:27 <jrandolf> -q
16:22:33 <jrandolf> q-
16:23:13 <AutomatedTester> whimboo: just to be sure if you load a page you might not know the browsing context? if the page is opened via window.open you would have to reload the page to get preload scripts into it?
16:23:58 <AutomatedTester> orkon: Yes that is correct. This is mostly for iframes. We just wanted to check people's opinions and are happy to add a use case for this
16:24:02 <AutomatedTester> ack next
16:24:30 <AutomatedTester> jgraham: I assume you want preload scripts to work after navigation?
16:24:34 <AutomatedTester> orkon: yes
16:25:05 <AutomatedTester> jgraham: do you want this to work after document.open?
16:25:25 <AutomatedTester> orkon: that shouldn't affect things here
16:25:39 <AutomatedTester> jgraham: ok that's the answer I was hoping for
16:25:43 <AutomatedTester> q?
16:26:37 <AutomatedTester> Topic: How would we approach file upload/filling out the file inputs?
16:26:41 <orkon> q+
16:26:49 <AutomatedTester> ack next
16:27:43 <whimboo> https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/files
16:27:43 <jgraham> q+
16:27:54 <AutomatedTester> orkon: for puppeteer we have 2 requirements. 1: we should intercept the dialog. 2. we should be able to handle the file name
16:27:56 <AutomatedTester> ack next
16:28:09 <simonstewart> q+
16:28:37 <AutomatedTester> jgraham: setting the file path directly is what webdriver classic does already so we need to make sure that still works as is
16:29:13 <AutomatedTester> orkon: we show the event in puppeteer which is then allows people to set the path on the element referenced in the event
16:29:27 <AutomatedTester> jgraham: I assume this happens after an input action
16:30:19 <AutomatedTester> jgraham: I don't see an issue here but I am not sure if this blocking in the UI
16:30:31 <mathiasbynens> present-
16:30:36 <AutomatedTester> ack next
16:31:00 <AutomatedTester> simonstewart (IRC): one of the things that people don't always like setting the file input
16:31:13 <jrandolf> q+
16:31:29 <AutomatedTester> ... but they still want to have a way to upload and we don't always have an ideal solution for our users
16:31:35 <AutomatedTester> ack next
16:32:09 <simonstewart> q+
16:32:29 <AutomatedTester> jrandolf: regarding drag and drop. We could implement drag info into the browser. but that's more of a drag and drop issue
16:32:34 <AutomatedTester> ack next
16:32:48 <jrandolf> q+
16:33:00 <jrandolf> q-
16:33:29 <AutomatedTester> simonstewart (IRC): drag and drop is a huge can of worms if we can avoid that. I think making sure we can handle the upload via a JS driven element is really important and we should make sure that we have that case covered
16:33:38 <AutomatedTester> q?
16:33:54 <JimEvans> q+
16:34:02 <AutomatedTester> ack next
16:34:59 <AutomatedTester> Jim Evans: THere is a little prior art here for when a user prompt is raised in the spec
16:35:01 <AutomatedTester> ... so perhaps we can do a very similar process can be done for file inputs
16:35:50 <AutomatedTester> topic: Support for cookie handling
16:36:04 <AutomatedTester> github: https://github.com/w3c/webdriver-bidi/issues/287
16:37:03 <AutomatedTester> jgraham: This is something that we need to make progress on this. It is a high priority on the roadmap
16:37:13 <AutomatedTester> ... this is the biggest missing piece so far
16:37:30 <orkon> q+
16:38:08 <AutomatedTester> ... I think because in the previous webdriver it causes issues for our users
16:38:32 <AutomatedTester> ... and we need to make sure that we have it work well in all browsers
16:38:47 <orkon> q-
16:38:47 <AutomatedTester> ... There is a draft PR up
16:39:03 <AutomatedTester> ... could everyone start reading the draft PR so we can have a much longer discussion at TPAC
16:39:58 <AutomatedTester> topic: Allow creating new browsing profiles/contexts
16:40:12 <AutomatedTester> github: https://github.com/w3c/webdriver-bidi/issues/289
16:41:06 <AutomatedTester> orkon: THis is something that has come up as a need for puppeteer. We would like to work on this for our users
16:41:39 <jgraham> q+
16:41:47 <AutomatedTester> ... we also know that it is not fully compatible across browsers but I wonder if there are ideas about how we can get started with this
16:41:53 <AutomatedTester> ack next
16:42:29 <AutomatedTester> jgraham: I think the way to make progress here is enumerate the properties that we depend on in puppeteer
16:43:16 <AutomatedTester> ... it's not very clear to me are these private browsing "areas" or is it purely separate storage
16:44:02 <AutomatedTester> ... are they going to be named? is the name accessible? It's currently hard to know what properties are needed. E.g. In firefox is it private browsing or containers?
16:44:43 <AutomatedTester> ... I think that we should have an action to collect those things so we can work with other browsers to make sure that we know how this all maps
16:45:35 <AutomatedTester> action: Orkon - Collect these properties needed and put it in the issue with use cases of how people would use it
16:45:35 <AutomatedTester> orkon: I will go collect these up
16:45:35 <AutomatedTester> q?
16:47:16 <AutomatedTester> topic: History navigation events
16:47:27 <AutomatedTester> github: https://github.com/w3c/webdriver-bidi/issues/502
16:47:57 <AutomatedTester> jgraham: the question here is how do we want to expose history navigation in the API
16:48:14 <AutomatedTester> ... at the moment we have specific events
16:48:27 <AutomatedTester> ... for history and for fragments
16:48:58 <AutomatedTester> ... we don't have any events for the old history or the new history API in the browser. The latter is only in chromium
16:49:41 <AutomatedTester> ... so how should we expose this to an API? Should we have 1 event or map to a DOM event?
16:49:49 <AutomatedTester> q?
16:49:49 <orkon> q+
16:49:51 <AutomatedTester> ack next
16:50:27 <AutomatedTester> orkon: in CDP we don't distinguish between fragments and history
16:50:39 <AutomatedTester> ... we only have 1 type of event that people can listen to
16:51:01 <AutomatedTester> ... I don't think we have a usecase for more detailed events than that
16:51:04 <AutomatedTester> q?
16:52:11 <simonstewart> q+
16:52:24 <AutomatedTester> automatedtester: jgraham do you want to see what CDP is doing and see if that is sufficient?
16:52:52 <AutomatedTester> jgraham: yea maybe, I can see some cases where we want different types of events
16:53:37 <AutomatedTester> ... and puppeteer could always take the different events and map it to a single API
16:54:03 <orkon> q+
16:54:17 <AutomatedTester> ... I think we should make sure that we design it forward looking as much as possible
16:54:20 <AutomatedTester> ack next
16:55:10 <AutomatedTester> simonstewart (IRC): speaking with my selenium hat on I think having a single event type is much easier DX for our users
16:55:37 <AutomatedTester> ... and it is easier to implement and the exact opposite of jgraham was saying
16:55:39 <AutomatedTester> ack next
16:56:12 <AutomatedTester> orkon: I am not up to date with the new API and I wonder if there are ways we can do this with script evaluation
16:56:56 <AutomatedTester> jgraham: I think there are ways to do it but not sure they are sensible and it would be better to expose this directly in our API
16:57:46 <AutomatedTester> ... e.g. if we wanted to do a task after a history event has completed they could do it even if it wasnt initiated via a webdriver API
16:57:48 <AutomatedTester> q?
16:59:36 <orkon> present-
16:59:59 <AutomatedTester> rrsagent, make minutes
17:00:00 <RRSAgent> I have made the request to generate https://www.w3.org/2023/08/09-webdriver-minutes.html AutomatedTester
18:21:20 <jgraham> rrsagent: bye
18:21:20 <RRSAgent> I see 2 open action items saved in https://www.w3.org/2023/08/09-webdriver-actions.rdf :
18:21:20 <RRSAgent> ACTION: David - Make sure agenda is ready ahead of time and organsie the remote participation links [1]
18:21:20 <RRSAgent>   recorded in https://www.w3.org/2023/08/09-webdriver-irc#T16-11-01
18:21:20 <RRSAgent> ACTION: Orkon - Collect these properties needed and put it in the issue with use cases of how people would use it [2]
18:21:20 <RRSAgent>   recorded in https://www.w3.org/2023/08/09-webdriver-irc#T16-45-35
18:21:25 <jgraham> zakim, bye
18:21:25 <Zakim> leaving.  As of this point the attendees have been AutomatedTester, JimEvans, orkon, mathiasbynens, jgraham, jdescottes, sasha, whimboo, lightning00blade, simonstewart, jrandolf,
18:21:25 <Zakim> Zakim has left #webdriver
18:21:28 <Zakim> ... gsnedders, cb