Vaadin version: 25.3
Testing: com.vaadin:browserless-test-shared (JUnit 6 browserless tests)
I’m writing a browserless test for a Grid that listens for addItemDoubleClickListener and uses event.getColumn() to decide which detail view to navigate to (different columns open different edit views on double-click).
GridTester.doubleClickRow(int) (and its overloads with MouseButton/MetaKeys) always fires an ItemDoubleClickEvent with column = null, because the underlying Grid<T>._doubleClickItem(rowIndex, button, ...) in com.vaadin.browserless.component.Grid.kt hardcodes null for the column argument when constructing the event. There’s no overload that accepts a Grid.Column<*> or a column key.
This is inconsistent with the single-click side: Grid<T>._clickItem has overloads that accept a Grid.Column<*> or a columnKey: String, so GridTester/ItemClickEvent testing can target a specific column — but the double-click equivalent has no such option.
Is there a supported way to simulate a double-click on a specific grid cell/column today (e.g. some lower-level API I’m missing), or is this a genuine gap in browserless-test-shared? If it’s a gap, is a column-targeted doubleClickRow(int row, String columnKey) (mirroring the click-side API) on the roadmap, or should I file this as a feature request/bug?
Thanks!