When no argument is passed to the .click interaction command, the webdriver command should also have no argument

Indeed webdriver.io has a different behavior when the argument is not
undefined.

Fixes #8931

Author: julienw

packages/browser-webdriverio/src/commands/click.ts

@@ -4,10 +4,10 @@ import type { UserEventCommand } from './utils'
 export const click: UserEventCommand<UserEvent['click']> = async (
   context,
   selector,
-  options = {},
+  options,
 ) => {
   const browser = context.browser
-  await browser.$(selector).click(options as any)
+  await browser.$(selector).click(options)
 }
 
 export const dblClick: UserEventCommand<UserEvent['dblClick']> = async (

test/browser/test/userEvent.test.ts

@@ -29,6 +29,10 @@ describe('userEvent.click', () => {
 
     expect(onClick).toHaveBeenCalled()
     expect(dblClick).not.toHaveBeenCalled()
+
+    onClick.mockClear()
+    await userEvent.click(button, { button: 'right' })
+    expect(onClick).toHaveBeenCalled()
   })
 
   test('correctly doesn\'t click on a disabled button', async () => {