fix: Fix click count in TestBenchElement#click()

[TatuLund]

No description provided.

[Copilot]

Pull request overview

This PR adjusts how TestBenchElement#click() triggers click events so that Flow click listeners receive the correct click count, and adds an integration test view plus tests to verify single and double click behavior and focus.

Changes:

• Update TestBenchElement.click() to dispatch a custom MouseEvent('click') with an explicit detail value instead of calling the element’s click method via callFunction("click").
• Introduce a ButtonView test route that exposes a native button with single-click, double-click, and focus listeners reflecting click count and focus state in the DOM.
• Add ButtonIT integration tests to validate single-click and double-click behavior (including click count and focus) via NativeButtonElement.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
vaadin-testbench-shared/src/main/java/com/vaadin/testbench/TestBenchElement.java	Changes click() to use an inline JavaScript text block that dispatches a MouseEvent('click', { detail: 1, ... }) on the element, preserving focus and existing fallback behavior.
vaadin-testbench-integration-tests/src/test/java/com/vaadin/tests/elements/ButtonIT.java	Adds JUnit integration tests that exercise NativeButtonElement.click() and .doubleClick() and assert correct click count and focus side effects.
vaadin-testbench-integration-tests/src/main/java/com/vaadin/testUI/ButtonView.java	Adds a Flow @Route view with a native button wired with single-click, double-click, and focus listeners that update spans used by the new tests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mcollovati]

I created a branch on flow-components to simulate the issue with double-click throwing an exception with Grid when the clicked cell is not visible without scrolling.

The test fails with the current implementation. However, it passes with this change, but only if I reaplce scrollIntoView() method in autoScrollIntoView() with the following

Map<String, Object> params = Map.of("block", "end", "inline", "end");
callFunction("scrollIntoView", params);

[TatuLund]

The test fails with the current implementation. However, it passes with this change, but only if I reaplce scrollIntoView() method in autoScrollIntoView() with the following

I incorporated the change in the PR. Your test in Flow components looks ok to me.

[mcollovati]

To avoid potential incompatibilities, I would not change the scrollIntoView method. What about adding a new one that takes the options Map as a parameter?

[TatuLund]

What about adding a new one that takes the options Map as a parameter?

Ok. Done that.