MSEdgeDriver returns non W3C WebDriver compliant caps when creating a session.

[diemol]

Almost exactly like https://bugs.chromium.org/p/chromedriver/issues/detail?id=4129&sort=-id.

networkConnectionEnabled and msedge are returned when creating a session but they are not W3C WebDriver caps. These capabilities should be prefixed with ms:.

{
  "value": {
    "capabilities": {
      "acceptInsecureCerts": true,
      "browserName": "msedge",
      "browserVersion": "101.0.1210.53",
      "ms:edgeOptions": {
        "debuggerAddress": "localhost:50338"
      },
      "msedge": {
        "msedgedriverVersion": "101.0.1210.53 (019dbf6dd738aa1846d87f5734878db0ee9df370)",
        "userDataDir": "/var/folders/85/m0jdxw2j3yn9mrn_2dpnbsmm0000gn/T/.com.microsoft.edgemac.hl45kf"
      },
      "networkConnectionEnabled": false,
      "pageLoadStrategy": "normal",
      "platformName": "mac os x",
      "proxy": {},
      "setWindowRect": true,
      "strictFileInteractability": false,
      "timeouts": {
        "implicit": 0,
        "pageLoad": 30000000,
        "script": 30000000
      },
      "unhandledPromptBehavior": "accept and notify",
      "webauthn:extension:credBlob": true,
      "webauthn:extension:largeBlob": true,
      "webauthn:virtualAuthenticators": true
    },
    "sessionId": "023cccea54c09fca28b640da3dce06c7"
  }
}

[bwalderman]

Thank you for reporting this. We'll work with the ChromeDriver team to get this addressed in both browser drivers.

[diemol]

Thanks, @bwalderman!