15:35:36 RRSAgent has joined #webdriver 15:35:36 logging to https://www.w3.org/2021/10/13-webdriver-irc 15:35:45 RRSAgent: quiet 15:35:45 I'm logging. I don't understand 'quiet', AutomatedTester_. Try /msg RRSAgent help 15:36:26 RRSAgent: silence 15:38:35 Meeting: October 2021 WebDriver 15:38:50 chair: AutomatedTester 15:39:19 agenda: https://www.w3.org/wiki/WebDriver/2021-10-BiDi 15:39:35 Scribe: David Burns 15:39:45 scribenick: AutomatedTester 15:40:06 RRSAgent: create minutes 15:40:06 I have made the request to generate https://www.w3.org/2021/10/13-webdriver-minutes.html AutomatedTester_ 15:41:02 RRSAgent: Make logs public 15:41:08 RRSAgent: Make minutes v2 15:41:10 I have made the request to generate https://www.w3.org/2021/10/13-webdriver-minutes.html jgraham 15:41:31 RRSAgent: stop 16:00:11 RRSAgent: Make minutes v2 16:00:12 I have made the request to generate https://www.w3.org/2021/10/13-webdriver-minutes.html jgraham 16:00:59 present+ 16:01:38 present+ 16:02:30 present+ 16:03:43 present+ 16:04:03 brwalder has joined #webdriver 16:04:28 present+ 16:04:36 simonstewart has joined #webdriver 16:04:55 present+ 16:05:18 present+ 16:05:22 https://www.w3.org/wiki/WebDriver/2021-10-BiDi 16:05:49 Agenda: https://www.w3.org/wiki/WebDriver/2021-10-BiDi 16:06:34 ScribeNick: jgraham 16:06:37 Topic: TPAC 16:06:49 patrickangle_ has joined #webdriver 16:08:04 AutomatedTester: Nothing currently organised. But TPAC is remote so there's still the possibility to organise something. Do we want something extra for TPAC or is the current cadence OK? If we do need something, what do people want? Also Web Extensions want to speak to us, we should find a way to make that work. 16:08:36 q? 16:08:37 q? 16:08:44 q+ 16:10:03 ack jgraham 16:10:31 jgraham: No obvious need for an extra meeting from my side, but would be good to talk to WECG to see if there's the possibility to share work on some common functionality e.g. sandboxed scripts. 16:11:13 AutomatedTester: Don't want to overload with meetings. The current cadence seems OK to me, but I'll send out an email to check with the whole group. I'll also contact WECG. 16:11:37 ScribeNick: AutomatedTester: 16:11:38 ScribeNick: AutomatedTester 16:11:40 action: David to email wg about TPAC 16:11:52 action: david to email WECG to organise meeting 16:12:39 topic: formatted args support 16:12:42 github: (https://github.com/w3c/webdriver-bidi/issues/139 16:12:52 s/(// 16:13:09 github: https://github.com/w3c/webdriver-bidi/issues/139 16:13:54 jdescottes: I posted a question in an issue about formatted args supported 16:14:12 ... we looked across the implementation and there is no real interop here 16:14:38 q+ 16:14:39 ... and we looked at CDP and it [describes how that works] 16:14:57 ... and we saw that stringify doing different things in different browsers 16:15:27 ... so my question is do we want to standradize here or push it back to consumers? 16:15:28 q? 16:15:34 ack simonstewart 16:15:42 https://bugzilla.mozilla.org/show_bug.cgi?id=1731543#c9 has the clearest examples of what's going on here 16:15:55 simonstewart: I think we want to send back the formatted text to consumers 16:16:06 q+ 16:16:13 ... not everyone is going to be using JS 16:16:42 ... we can send back different things depending on the types and some of it could be relatively undefinied 16:17:25 ... additionally, we can send back larger groupds of data to help people not do a lot of small calls across the internet 16:17:27 q? 16:17:30 ack jgraham 16:17:57 jgraham: CDP already doesn't fill in the format specifiers over the wire 16:18:30 ... and doesn't on the surface it doesn't know about substitution 16:19:12 q+ 16:19:20 ... however there is a argumnet that makes all the clients do the work may not be worth it because we can simplify it on browser side 16:19:55 ... and there could be a potential interop problem if things are not the same 16:20:21 ... I think I am currently leaning on the client doing the substitutions as we have prior art in puppeteer 16:21:04 ... and maybe in the future we can get to a point where we start the allow people to ask for the formatting but 16:21:06 q+ 16:21:17 ... would prefer to do the simplier thing now (unformatted) 16:21:20 q? 16:21:25 ack simonstewart 16:21:56 simonstewart: I am not sure the formatting consistency is a real issue 16:22:32 ... it might be easier in the browser but there is a lot of work for clients and can lower the quality for end users if it is not implemented properly 16:23:18 ... if people are using the logs to be searched they will be looking for messages they injected specifically 16:23:21 q? 16:23:25 ack foolip 16:23:47 foolip: what is that cdp/marionette currently do? 16:24:24 jdescottes: You can go to the issue and see the differences in the implementations 16:25:06 q? 16:26:39 topic: Events for initial about:blank 16:26:58 github: https://github.com/w3c/webdriver-bidi/issues/141 16:27:31 jgraham: when we started looking at navigation we came across about:blank 16:28:06 ... so historically about:black has been an area of bad interop 16:28:06 q+ 16:28:13 ... and firefox is an outlier here 16:28:31 ack foolip 16:28:47 foolip: I have an opinion but does it really matter? 16:28:57 jgraham: I don't really know 16:29:07 ... I suspect it doesn't matter that much 16:30:15 ... [discusses a few different scenarios around events and loading of about:blank in different contexts] 16:30:47 foolip: On the web a person can create a new page and then observe it 16:31:15 ... so if people want it we should give it to them 16:31:29 ... there might be reasons, they can ignore if they want 16:31:54 jgraham: There is 1 case when you waant tocreate an about:blank and run some script 16:32:35 ... but there might be case where we dont care where you create a frame and with a url. about:blank is loaded first and then the url and that might confuse folks 16:32:36 I think hsivonen has had a lot of fun with about:blank and load events. 16:33:41 ... I think we can see what the browsers are doing and make sure we do the most interoperable thing 16:33:44 q? 16:34:29 topic: Sending data from the local end (client) to the remote end (browser) 16:35:20 github: https://github.com/w3c/webdriver-bidi/issues/140 16:36:14 jgraham: how do we serialise the arguments from the client to the browser 16:36:36 ... and this came up from a PR that sadym did 16:36:48 ... and we don't want to copy selenium 16:37:14 ... so if its an ID we will run it from what's stored 16:37:52 ... so do people have opinions on what is sent to the browser? 16:38:47 ... [describes the events and seriablisable args] 16:39:34 ... so we can either have the client have a look process or have a symetrical serialisation process 16:39:50 q+ 16:40:06 ack sadym 16:40:28 sadym: So my idea was to have 1 source of truth 16:40:44 ... and we mirror from the browser to the client 16:41:24 q+ 16:41:35 ... e.g. If I create an object on the client side and passed it to the browser what would happen 16:42:09 jgraham: so on the browser side it would look like a immutable platform object 16:43:08 ... we have some strong use cases for sending back full objects to the client and not that much in the other directions 16:43:31 q? 16:44:24 sadym: the parametere in the `invoke` do we need this object reference? In CDP there is an implementation but it seems to be syntatic sugar 16:44:48 jgraham: I agree with you for the initial implementation 16:45:06 ... although we should look and see what puppeteer/playwright do 16:45:15 q? 16:45:20 ack brwalder 16:45:46 brwalder: should we maintain object ideas on the client side 16:46:04 ... I agree with sadym here that the browser should be the source of truth 16:46:32 ... if we don't do that we have a lot of complexity on clients 16:47:01 ... [describes a scenario] 16:47:22 ... and I am not convinced the added complexity in browsers is worth it 16:47:50 q? 16:47:59 q+ 16:48:22 jgraham: I don't think there is a lot of enthusiam for supporting this now 16:48:34 ... so we'll do the simple thing which is great 16:48:37 ack sadym 16:49:39 sadym: one other scenario when a client receives an object with args and then sends it back the browser the args could be ignored 16:50:04 ... and there wouldnt be a collision with things going back and forth 16:50:16 q? 16:50:50 topic: Reminder there is an editorial meeting 16:52:35 RRSAgent: make minutes v2 16:52:35 I have made the request to generate https://www.w3.org/2021/10/13-webdriver-minutes.html jgraham 16:53:33 RRSAgent: bye 16:53:33 I see 2 open action items saved in https://www.w3.org/2021/10/13-webdriver-actions.rdf : 16:53:33 ACTION: David to email wg about TPAC [1] 16:53:33 recorded in https://www.w3.org/2021/10/13-webdriver-irc#T16-11-40 16:53:33 ACTION: david to email WECG to organise meeting [2] 16:53:33 recorded in https://www.w3.org/2021/10/13-webdriver-irc#T16-11-52