"Firing a synthetic mouse event" has steps that might not make sense for .click()

[domenic]

https://html.spec.whatwg.org/multipage/webappapis.html#windoworworkerglobalscope-mixin:windoworworkerglobalscope-5

6. Initialize event's ctrlKey, shiftKey, altKey, and metaKey attributes according to the current state of the key input device, if any (false for any keys that are not available).

and

8. event's getModifierState() method is to return values appropriately describing the current state of the key input device.

I kind of doubt that if I hold down Ctrl while the page calls .click(), that the resulting event will have ctrlKey set. If that is true (and we should test), it's quite surprising and the spec should note it.

If it's not true, as I suspect, then we need to fix up the definition of .click().