Closed rfay closed 3 weeks ago
Currently this add-on uses seleniarm/standalone-chromium in its own docker-compose.core-dev-selenium.yaml
But the ddev/ddev-selenium-standalone-chrome is well-maintained and provides these facilities.
What about requiring that add-on as a dependency instead of requiring the docker-compose.core-dev-selenium.yaml here?
Thanks for the suggestion! I'd like to keep control over the image version being used though, and I do intend to complete the firefox support :smiley_cat:
Currently this add-on uses seleniarm/standalone-chromium in its own docker-compose.core-dev-selenium.yaml
But the ddev/ddev-selenium-standalone-chrome is well-maintained and provides these facilities.
What about requiring that add-on as a dependency instead of requiring the docker-compose.core-dev-selenium.yaml here?