Skip to content

Conversation

web-padawan
Copy link
Member

Description

The following test fails locally but for some reason passes in CI:

test/integration/grid-pro-custom-editor.test.js:

 ❌ grid-pro custom editor > custom-field > should not stop editing when switching between fields using mouse
      AssertionError: expected null to be truthy
        at n.<anonymous> (test/integration/grid-pro-custom-editor.test.js:305:71)

Chromium: |██████████████████████████████| 28/28 test files | 268 passed, 1 failed, 1 skipped

I wasn't able to figure out why it happens but it's somehow related to removal of Lumo from ITs.
After some debugging I figured out that test passes after adding line-height to the field.

Type of change

  • Test

@@ -63,6 +63,8 @@ describe('grid-pro custom editor', () => {
// NOTE: using `innerHTML` doesn't work due to the timing issue in custom-field
// See https://github.com/vaadin/web-components/issues/7871
const field = document.createElement('vaadin-custom-field');
// TODO: workaround sendMouse test failing locally in Chrome
field.style.lineHeight = '1.5';
Copy link
Contributor

@vursen vursen Jul 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the grid cells are rendering with 0 height, which is causing this issue. I would suggest adding the same fix used in other tests:

vaadin-grid-pro::part(cell) {
  min-height: 36px;
}

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, updated.

Copy link

@web-padawan web-padawan merged commit 0096374 into main Jul 10, 2025
10 checks passed
@web-padawan web-padawan deleted the test/custom-field-grid-pro branch July 10, 2025 11:16
@vaadin-bot
Copy link
Collaborator

This ticket/PR has been released with Vaadin 25.0.0-alpha3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants