search

w3c / webdriver-bidi

Bidirectional WebDriver protocol for browser automation
https://w3c.github.io/webdriver-bidi/
378 stars 42 forks source link

Add subscription IDs to events #810

Open OrKoN opened 2 weeks ago

OrKoN commented 2 weeks ago

Preview | Diff

Mr0grog commented 2 weeks ago

Is there any chance this could add a list of session.Subscription to every event, which would also help solve #754?

css-meeting-bot commented 1 week ago

The Browser Testing and Tools Working Group just discussed Subscription IDs for events.

The full IRC log of that discussion <AutomatedTester> topic: Subscription IDs for events
<AutomatedTester> github: https://github.com/w3c/webdriver-bidi/pull/810
<AutomatedTester> orkon: this is a continuation of the previous topic
<AutomatedTester> ... I have been reworking this to make sure that we can inherit events
<jgraham> q+
<AutomatedTester> ... I have tried to get all the use cases but I am not sure that I ahve got them all
<AutomatedTester> ... should we add subscription IDs or should we use the current way of doing it without IDs
<AutomatedTester> ack next
<AutomatedTester> jgraham: I like the subscription id approach is good
<AutomatedTester> ... jdescottes brought this up for when working on tests so we can unscribe from events that are not related to what we are wroking on. e.g. harness events vs user events
<AutomatedTester> ... <describes a use case where we subscribe events from a list and then diff them>
<AutomatedTester> ... it might be easier to have it just as a list of events we want to handle
<AutomatedTester> q?