15:53:45 <RRSAgent> RRSAgent has joined #webdriver
15:53:49 <RRSAgent> logging to https://www.w3.org/2024/07/10-webdriver-irc
15:56:23 <AutomatedTester> meeting: WebDriver July 2024 Meeting
15:56:26 <AutomatedTester> agenda: https://www.w3.org/wiki/WebDriver/2024-07-BiDi
15:57:10 <orkon> orkon has joined #webdriver
15:57:33 <AutomatedTester> scribe: David Burns
15:57:43 <AutomatedTester> scribeNick: AutomatedTester
15:57:46 <AutomatedTester> present+
15:58:29 <AutomatedTester> rrsagent,  make logs world-visible
15:58:42 <jimevans> jimevans has joined #webdriver
15:58:47 <AutomatedTester> Chair: David Burns
15:59:09 <AutomatedTester> rrsagent, draft minutes
15:59:10 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/10-webdriver-minutes.html AutomatedTester
15:59:18 <jimevans> present+
16:00:39 <orkon> present+
16:01:23 <jgraham> present+
16:03:52 <jgraham> Agenda: https://www.w3.org/wiki/WebDriver/2024-07-BiDi
16:04:19 <jgraham> RRSAgent make minutes
16:04:29 <sasha> sasha has joined #webdriver
16:04:50 <jdescottes> jdescottes has joined #webdriver
16:05:15 <jdescottes> present+
16:05:24 <sasha> present+
16:06:27 <jugglinmike> jugglinmike has joined #webdriver
16:06:31 <AutomatedTester> Topic: TPAC
16:06:38 <jugglinmike> present+ jugglinmike
16:06:58 <AutomatedTester> https://www.w3.org/calendar/tpac2024
16:07:04 <gsnedders_irc> gsnedders_irc has joined #webdriver
16:07:55 <jdescottes> jdescottes has joined #webdriver
16:11:30 <AutomatedTester> AutomatedTester: We're going to TPAC. All the details are in the link about what days we will be there
16:12:01 <AutomatedTester> gsnedders_irc: can we find out who will be travelling so we can make the remote folks from Europe not have to be around till 6pm PST
16:12:16 <AutomatedTester> ACTION: David to find out who will be remote for the meetings
16:12:41 <AutomatedTester> topic: setWindowRect where position can't be set
16:12:56 <AutomatedTester> github: https://github.com/w3c/webdriver/issues/1826
16:13:26 <AutomatedTester> jgraham: This is initially about classic but will affect setWindowRect
16:13:39 <AutomatedTester> s/setWindowRect/bidi
16:14:06 <AutomatedTester> ... in linux there are times where the answers we are returned does not always match reality
16:14:13 <AutomatedTester> q+
16:14:36 <AutomatedTester> ... so for the setter, should it fail or should it ignore you?
16:15:03 <AutomatedTester> ... we are doing this in WPT and run it on wayland it will fail and gecko tests time out
16:15:19 <AutomatedTester> ... Mozilla has a major push to fix because of the above
16:16:33 <AutomatedTester> ... there are different scenarios in the issue that we can do
16:16:37 <AutomatedTester> ack next
16:17:57 <AutomatedTester> AutomatedTester: what happens if you set it and it fails?
16:19:35 <orkon> q+
16:19:46 <AutomatedTester> jgraham: in wayland it allows either x,y or size. not both
16:20:46 <AutomatedTester> AutomatedTester: if I remember that we do the best case here. E.g. try pass it and then do best guess. The main reason was mobile can-'t do any of these things so I am happy with it returning where it thinks everything is
16:20:57 <AutomatedTester> ack next
16:22:43 <AutomatedTester> orkon: it sounds like apply as much as possible but we can error. I know we the browser will not always be able to do this. Our position is we can return without setting the position and returning the value of where it thinks it is
16:23:52 <AutomatedTester> jgraham: I think that we need to make sure that we dont break tests. I don't think we need to make this fatal if things don't work out
16:24:05 <AutomatedTester> ... and set the value and then return where it thinks it is
16:25:42 <AutomatedTester> gsnedders_irc: do we expect the return the command with error? on mobile we can return errors
16:25:58 <AutomatedTester> AutomatedTester: I am happy to return the 0, 0 and window size and not error?
16:26:58 <AutomatedTester> gsnedders_irc: do we expect people to run desktop tests on mobile?
16:27:35 <AutomatedTester> automatedtester: yes, 80% of tests will work that way unless people think there are feature differences between the platforms. They want write once run everywh
16:27:40 <AutomatedTester> ...ere
16:28:40 <AutomatedTester> automatedtester: do we want it to try on desktop and reutn the values it gets to and on mobile error
16:29:12 <AutomatedTester> jgraham: yes. There are some imprementation defined ways to error
16:30:09 <AutomatedTester> topic: Network request ids for auth + CORS preflight
16:30:20 <AutomatedTester> github: https://github.com/w3c/webdriver-bidi/issues/722
16:31:20 <AutomatedTester> jgraham: for netwroking intercepts and logging. In the case of redirects we would have a reuqest id that was the same for the whole chain or requests
16:31:35 <AutomatedTester> ... what we didn't consider was http auth and cors preflight
16:31:56 <AutomatedTester> ... for cors preflight it looks like a separate reuqest
16:32:08 <AutomatedTester> ... for http auth it looks like the original requests
16:32:31 <AutomatedTester> .... the spec handles this in 3 different ways in the spec
16:33:06 <AutomatedTester> ... this has been discussed in the issue. It is unclear what we should do next?
16:34:30 <AutomatedTester> ... <explains different ways with request ids, added fields on the objects>
16:34:44 <orkon> q+
16:34:54 <AutomatedTester> ... I would like to know if people have opinions on what approach and what invariants we want to support
16:34:57 <AutomatedTester> ack next
16:35:46 <AutomatedTester> orkon: I haven't looked into the issue before the meeting. In the puppeteer we have always considered cors to have separate ids
16:36:42 <AutomatedTester> ... if there is auth we have and the dialog is handled and the same id is in the events
16:36:57 <AutomatedTester> ... if there is an error we expect a new request id
16:37:29 <AutomatedTester> ... looking at puppeteer we do a mix of wha tthe spec has
16:37:59 <AutomatedTester> jgraham: for cors request preflight can be handled as a special case
16:38:17 <AutomatedTester> ... for auth we should treat it like a redirect
16:39:10 <AutomatedTester> ... which appears to be different to what puppeteer does with cdp. I think jdescottes proposal seems to handle this scenario
16:39:35 <orkon> q+
16:39:43 <AutomatedTester> ... our concern is if there is a auth and the credentials are wrong and it gets itnto a loop doing that over and over
16:39:45 <AutomatedTester> ack next
16:40:10 <AutomatedTester> orkon: if we add the auth count is it for per redirect or for the whole chain?
16:40:35 <AutomatedTester> ... if we add a parameter that could cause problems down the line
16:40:57 <AutomatedTester> jgraham: I agree a multipart key makes it more complex
16:41:45 <AutomatedTester> ... and if chain has the count can handle the count
16:41:50 <AutomatedTester> q?
16:41:55 <jdescottes> q+
16:42:09 <AutomatedTester> ack next
16:42:23 <AutomatedTester> jdescottes: I was thinking of another design
16:42:35 <AutomatedTester> ... one thing we can do is always have a unique id
16:43:15 <AutomatedTester> ... and we could have a parent that knows where it could be from and where it is going. E.g. parent for redirect or parent for auth
16:43:36 <AutomatedTester> jgraham: if we do that it creates a new set of invariants and breaks clients
16:45:19 <AutomatedTester> ACTION: Please read the issue and leave comments (all)
16:45:25 <AutomatedTester> topic: File dialog handling
16:45:35 <AutomatedTester> github: https://github.com/w3c/webdriver-bidi/pull/568
16:46:11 <orkon> q+
16:46:20 <AutomatedTester> jgraham: This is more of aquestion. The user prompt handling is in place now we can work on this
16:46:37 <AutomatedTester> ack next
16:46:57 <AutomatedTester> orkon: Maksim will be working on this and will update the PR
16:47:18 <AutomatedTester> ... what we will want now is that if a dialog is opened that we fire an event back to the client
16:47:39 <AutomatedTester> ... and it is similar to the PR
16:48:25 <AutomatedTester> ... we don't have the ability to handle this at the moment because of the way that CDP works but we hope to have it updated for bidi
16:48:28 <AutomatedTester> q?
16:48:28 <jgraham> Using the userPromptOpened events
16:48:47 <AutomatedTester> jgraham: that sounds great! I was hoping for that
16:49:02 <AutomatedTester> topic: Navigable rewrite
16:49:11 <AutomatedTester> github: https://github.com/w3c/webdriver-bidi/pull/729
16:49:40 <jgraham> q+
16:49:41 <AutomatedTester> orkon: the last time we were updating to use navigables instead of contexts
16:49:53 <AutomatedTester> ... it would be good if folks can review it
16:50:04 <AutomatedTester> ack next
16:50:35 <AutomatedTester> jgraham: I looked earlier and it mostly looks right. I will try read it again very soon. Thanks for doing all the editorial work
16:50:53 <AutomatedTester> orkon: I've updated links etc
16:54:55 <orkon> present-
16:55:04 <jgraham> RSSAgent make minutes
16:55:09 <jgraham> zakim, bye
16:55:09 <Zakim> leaving.  As of this point the attendees have been AutomatedTester, jimevans, orkon, jgraham, jdescottes, sasha, jugglinmike
16:55:09 <Zakim> Zakim has left #webdriver
16:55:23 <jgraham> RRSAgent make minutes
16:55:42 <jgraham> RRSAgent: make minutes
16:55:44 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/10-webdriver-minutes.html jgraham
16:56:44 <jgraham> RRSAgent: bye
16:56:44 <RRSAgent> I see 2 open action items saved in https://www.w3.org/2024/07/10-webdriver-actions.rdf :
16:56:44 <RRSAgent> ACTION: David to find out who will be remote for the meetings [1]
16:56:44 <RRSAgent>   recorded in https://www.w3.org/2024/07/10-webdriver-irc#T16-12-16
16:56:44 <RRSAgent> ACTION: Please read the issue and leave comments (all) [2]
16:56:44 <RRSAgent>   recorded in https://www.w3.org/2024/07/10-webdriver-irc#T16-45-19