There isn’t a real set that I am aware of. We have historically left the adding of the WebDriver APIs to the spec that is adding the features and then we would be called in for wider reviews to make sure it sticks to the values of WebDriver.
David
On Mar 7, 2020, 2:32 AM +0000, John Jansen <John.Jansen@microsoft.com>, wrote:
> Is there a set of principles around when/how WebDriver emulation should be added for new features, especially those that are exposing new OS and/or hardware capabilities?
>
> At Microsoft, we’re starting the process[1] for contributing our dual screen APIs to Chromium, but I don’t have a good sense of what is typically expected of WPT tests for new features like this. I know we’ve talked about this on different occasions, but I don’t think we’ve ever written something into a spec or design document.
>
> -John
>
> [1] https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/Foldables/explainer.md
>