3/24/2023 0 Comments Safari technology preview 135However, as long as Safari supports the two latest versions of macOS, this isn't a big problem as long as upgrading isn't blocked like it is now. It seems to me like this can only be fixed by testing Safari in public CI systems in the macOS and Safari release process, because once a problem is in a stable release, we end up blocked for a very long time.įinally, Azure Pipelines and other public CI systems take time to support a new version of macOS, and we as the web-platform-tests project have no influence over this. The way that WPT has to use Safari is different from a web developer running tests on their own machine. There hasn't been a problem recently, but infrastructure/ tests don't work with Safari Technology Preview 68 #13800 is an example from a few years ago. The WebDriver implementation has to be pretty solid.But if there was a way to provide the certificate to safaridriver and it was only valid for automated testing, that would solve the problem too. This was possible using sudo security add-trusted-cert until macOS 11.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |