Jason Cheatham

I'll take a look at Windows 10. Are you using the selenium tunnel, or talking directly to the WebDriver through a null tunnel?

It works on Windows 10 with Selenium 3.141.59, msedgedriver 80.0.361.62, and Edge 80.0.361.62 when using Intern's SeleniumTunnel. Possibly there's some issue with Selenium running in grid mode (I haven't tested...

I _do_ get the InvalidArgument error when running over a grid.

Clicking works with bare msedgedriver and a null tunnel, so I'm guessing that Selenium in grid mode is choking on a bodyless POST rather than msedgedriver. I haven't seen anything...

Sending a `{}` when the `requestData` was empty gave me a slightly different error, but still an error: ``` InvalidArgument: [POST http://localhost:4444/wd/hub/session/7f2947b55b594f0b3f0e2b513ca3fb40/element/902432f4-fb73-41bc-8c81-32b42b236f53/click / "{}"] invalid argument: missing command parameters ```...

Passing `{ id: }` as the request data for `/element//click`, as suggested in https://github.com/nightwatchjs/nightwatch/pull/2122, does appear to work. Selenium does care about the `id` property (it's not just looking for...

> maybe because I specified it as {} rather than a string "{}" Good catch, maybe the `id` isn't necessary, even if it has to be valid if present.

Intern doesn't yet have comprehensive W3C mode, just W3C fixups for problematic commands. This issue will take care of part of that (using W3C semantics by default). #1027 is focused...

Yet another reason the reporter system needs an overhaul.

This is based on discussion in #1088