You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After executing the test browser should stay open and other features such as Pick locator should still be working:
playwright-show-browser-working.mp4
Actual
Browser immediately closes once test finishes:
playwright-show-browser-not-working.mp4
Notes
I'm really not sure whether the chrome extensions is to blame here but I've put that into the title as this was my use case.
It might be just the const context = await chromium.launchPersistentContext("", { ... }) or something else.
It also might be that it is necessary to update the code on my side, but in this case what changes should be made? And also maybe it would be healthy to update the documentation?
The text was updated successfully, but these errors were encountered:
@lukaskl This is because you manually launch the browser with chromium.launchPersistentContext() and then manually close it with context.close().
Reuse browser mode in VSCode extension only works with regular contexts that are provided by the test runner out of the box, i.e. with built-in page and context. I don't think it will work for your scenario in the near future, sorry.
Context:
1.30.0
Mac
v18.12.1
1.74.3
(Universal), Commit:97dec172d3256f8ca4bfb2143f3f76b503ca0534
1.0.6
Chromium
Code Snippet
I have created a repository where this issue is reproducible: https://github.com/lukaskl/playwright-report
But in short, when using chrome-extensions as suggested here Reused Browser (
Show browser
checkbox) stops to work.Describe the bug
Expected
After executing the test browser should stay open and other features such as
Pick locator
should still be working:playwright-show-browser-working.mp4
Actual
Browser immediately closes once test finishes:
playwright-show-browser-not-working.mp4
Notes
I'm really not sure whether the
chrome extensions
is to blame here but I've put that into the title as this was my use case.It might be just the
const context = await chromium.launchPersistentContext("", { ... })
or something else.It also might be that it is necessary to update the code on my side, but in this case what changes should be made? And also maybe it would be healthy to update the documentation?
The text was updated successfully, but these errors were encountered: