-
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
API v1.0 review #1348
Comments
Joel: Pavel: Yury: |
Joel Pavel |
Due to yarn, I believe this needs to take a download folder. @aslushnikov should remember the details. |
Let’s remove the shortcuts to errors on the browserTypes. We aren’t saving anyone anything in practice. TypeScript users need to import playwright for types already. I think other users are more likely to get passed a browser/context than a browser type. It feels out of place. |
Joel
When do I choose kill? Maybe we know based on how the server was launched (persistent)? If kill isn’t recommended, maybe we can let people do it through the process if they need to. Dmitry
|
s/sendCharacters/insertText |
@JoelEinbinder
@JoelEinbinder killing is involved across OS'es (e.g. on win we use |
So if I am in SIGTERM I call kill, otherwise I call close? If I’m in sigterm and I don’t do anything, will we leak processes? |
@JoelEinbinder the comparison table between the two:
By default, PW handles If parent node.js process terminates, Playwright will kill the launched browser. |
Returns all pages which have been initialized already. References #1348.
Playwright ✅
Browser ✅
BrowserContext ✅
BrowserType ✅
BrowserServer ✅
Worker ✅
A11Y ✅
Selectors
Response ✅
Request ✅
Mouse ✅
Keyboard ✅
Dialog ✅
ConsoleMessage ✅
JSHandle ✅
ElementHandle ✅
Frame ✅
Page ✅
CDPSession ✅
ChromiumCoverage ✅
ChromiumBrowserContext✅
ChromiumBrowser ✅
The text was updated successfully, but these errors were encountered: