Web components testing for legacy browsers #710
Replies: 1 comment 3 replies
-
Thanks for raising this @fernandofranca! As mentioned in the Playwright docs, the browser version is controlled by the Playwright dependency in the repo. To add to this, Playwright uses a generic WebKit browser and not the branded Safari browser, as noted here It looks like Percy have recently introduced a new feature that allows you to specify a browser version, and your test is then executed on hardware maintained by Percy. It looks like this only supports test frameworks that support W3C Protocol (WebDriver being the most popular), with no indication of if/when Playwright will be supported. https://docs.percy.io/docs/integrate-functional-testing-with-visual-testing#limitations |
Beta Was this translation helpful? Give feedback.
-
On the back of the
DSW-1013 - Implement dialog polyfill
ticket, I created theDSW-1073 - Add tests for Modal component dialog polyfill
.Since the dialog polyfill was added in order to improve legacy browser support, especially for Safari 14, it seems fair to test it in that browser.
During refinement, we tried to discuss the feasibility of that and agreed to create a discussion before refining the ticket.
The intent of the discussion is to check if it's technically reasonable, to have tests focused on specific browser versions.
Beta Was this translation helpful? Give feedback.
All reactions