Alex Rudenko

@domenic would you have a chance to review this PR? Thanks!

Partitioning should be accounted for in the WebDriver BiDi spec https://w3c.github.io/webdriver-bidi/#module-storage

@johannhof the spec allows extending the partitionKey with implementation-specific keys (e.g., hasCrossSiteAncestor). I have been starting to add the implementation for Chromium here https://github.com/GoogleChromeLabs/chromium-bidi/pull/2437 but have not finished it. If...

Related https://github.com/w3c/webdriver-bidi/issues/686

we do use all.cddl to generate [TypeScript types](https://github.com/GoogleChromeLabs/webdriver-bidi-protocol) and validation code in [chromium-bidi](https://github.com/GoogleChromeLabs/chromium-bidi/blob/main/src/protocol-parser/generated/webdriver-bidi.ts#L29). I believe all.cddl helps to avoid duplication of definitions which are marked as both local and remote.

The current plan to only add the local and remote indexes sounds good to me. One concern will be that there are currently 38 types that are both local and...

> Could you suggest an annotation mechanism? Not really, therefore, I think the current proposal is good.

@tidoust with our tooling we validate per command/event so we do not use the entire CDDL document for validation. I think if we want to support this use case the...

My understanding was that "trying" causes an early return of the algorithm where it is used. So if "merge capabilities" returns an error while "trying to merge capabilities", "process capabilities"...

Yeah, I found it surprising too but other interpretations make many parts of the spec (and also the bidi spec) broken in the way you described. The definition mentions that...