-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Other Browsers #647
Comments
We've been experimenting with different browsers and Playwright. |
I can confirm that these browsers are working:
but these not:
A working Opera version would be probably useful. |
@mxschmitt Hey, how to execute playwright with Edge Canary? Could you share that knowledge somewhere? |
Hey! I created a blog post about it, let me know if I forgot something. |
Hey @mxschmitt, |
Hi, my blog post only relates to Chromium based browsers. For Firefox or WebKit it's not possible to use own versions since Playwright internally injects there some wrappers to provide the APIs to automate it on compile time. |
How to launch opera browser in playwright?? |
Use Chromium to launch a browser and set your opera as a executable path when launching chromium. |
can you please share any example for this?
…On Wed, Apr 6, 2022 at 2:42 PM Max Schmitt ***@***.***> wrote:
How to launch opera browser in playwright??
Use Chromium to launch a browser and set your opera as a executable path
when launching chromium.
—
Reply to this email directly, view it on GitHub
<#647 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AX5QRNPGWQUV62DDK6YHYD3VDVIRLANCNFSM4KLN5YUA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
const browser = await playwright.chromium.launch({
executablePath: '/foo/bar/foobar'
}); this then depends on which OS you use, on Windows its e.g. on C:/Programs etc. on mac in /Applications etc. |
Mega issue to discuss playwright support for more platforms.
Older versions of our core browsers
As we upstream our patches and time goes on, the current versions of the browsers playwright supports will naturally be the older versions. Firefox ESR is supported for up to a year though, so we might get some value by specifically releasing an older version.
Branded Chromium
These should just work today by specifying
executablePath
and running with thechromium
object. They provide some small value over testing against the Chromium we download because they turn on different feature flags, and can play different media types. We could be doing more to help people with compatibility between the playwright package version and the specific branded browser they have.Electron
Electron is supported with
playwright-electron
package.Mobile Browsers
Right now we fake these browsers. It would be cool to be able to run tests directly against them. Maybe we can use the IOS simulator?
Internet Explorer
IE is still around somehow, and people want to test against it. The new Edge is based on Chromium, but still has an IE mode. It's very unlikely we would get our full feature set into IE. But having a small playwright-compatible subset of features could help tide people over until IE finally goes away. We could potentially wrap the work that has been done on WebDriver here.
The text was updated successfully, but these errors were encountered: