WebDriver/2019-05-BiDi
The Browser Testing and Tools Working Group teleconference
Observers are welcome to attend our group meeting. If any observers are interested in participating in the work on the test suite or joining the group, we will happily assist with this.
The meeting will be minuted to the #webdriver IRC channel. All participants and observers are encouraged to join this channel in advance.
Dial in Details
Join Zoom Meeting https://browserstack.zoom.us/j/92669701535?pwd=a29INjBtV3lodENhbU8xWGtpTXFsUT09
Meeting ID: 926 6970 1535
Password: 646924
One tap mobile
+13017158592,,92669701535#,,1#,646924# US (Germantown) +13126266799,,92669701535#,,1#,646924# US (Chicago)
Dial by your location
+1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 929 436 2866 US (New York) +1 253 215 8782 US (Tacoma)
Meeting ID: 926 6970 1535
Password: 646924
Find your local number: https://browserstack.zoom.us/u/ad6en7ednW
Join by SIP
92669701535@zoomcrc.com
Join by H.323
162.255.37.11 (US West) 162.255.36.11 (US East) 115.114.131.7 (India Mumbai) 115.114.115.7 (India Hyderabad) 213.19.144.110 (EMEA) 103.122.166.55 (Australia) 209.9.211.110 (Hong Kong China) 64.211.144.160 (Brazil) 69.174.57.160 (Canada) 207.226.132.110 (Japan)
Meeting ID: 926 6970 1535
Password: 646924
Agenda
The meeting will be held over Zoom. Details are above. The meeting will be at 5 PM BST/6 PM CEST/9 AM PST.
We are meeting Thursday and Friday from 09:00 CEST.
- Follow-ups from previous meeting
- "Brandon: So, AI is: getting an initial list of documents to work on before next meeting." (from notes)
- Spec organisation proposal (https://github.com/jgraham/webdriver-bidi created, using Bikeshed)
- Minimal feature to prove out in spec prose / impl prototype. Good if it's a useful addition to WebDriver and if it doesn't bring in too many issues. Candidates:
- Logging ("Log what's going on in the browser including console and JS errors" in goals)
- Notification of user prompts
- ???
- Discuss low-level transport protocol and message format: issue
- Supporting both HTTP and WebSocket messaging seems like it could be messy in the long term. Is it necessary? (zcorpan)