See:
The add-on currently ships selenium/standalone-chromium:138.0. Since Chrome 134, ChromeDriver's Element Click can return before a form submission has navigated, which makes any click-then-assert test flaky: the assertion runs against the previous page.
Drupal core pins selenium/standalone-chrome:133.0 in its own .gitlab-ci.yml for this reason (on main branch), so anyone running Drupal FunctionalJavascript or Drupal Test Traits tests against this add-on gets a browser that behaves differently from core CI, and has to override docker-compose.selenium-chrome.yaml locally (which ddev add-on get then reverts unless the generated marker is removed).
Would you consider pinning the image to 133.0 until the Chromium issue is resolved?
This could save a lot of people from debugging flaky tests while the bug is in chrome/chromium.
See:
The add-on currently ships selenium/standalone-chromium:138.0. Since Chrome 134, ChromeDriver's Element Click can return before a form submission has navigated, which makes any click-then-assert test flaky: the assertion runs against the previous page.
Drupal core pins selenium/standalone-chrome:133.0 in its own .gitlab-ci.yml for this reason (on main branch), so anyone running Drupal FunctionalJavascript or Drupal Test Traits tests against this add-on gets a browser that behaves differently from core CI, and has to override docker-compose.selenium-chrome.yaml locally (which ddev add-on get then reverts unless the generated marker is removed).
Would you consider pinning the image to 133.0 until the Chromium issue is resolved?
This could save a lot of people from debugging flaky tests while the bug is in chrome/chromium.