Principles for emulation for new features in WPT tests

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<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftEdge%2FMSEdgeExplainers%2Fblob%2Fmaster%2FFoldables%2Fexplainer.md&data=04%7C01%7CJohn.Jansen%40microsoft.com%7Cd2dab3d6c52542e6aa8108d7c23e984e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637191446508532418%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=9GyuaeCCiSndCbVsq6Hk2zWX4cdJ9iFbjzKXPeTE5iE%3D&reserved=0>