-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Take screenshots using Chrome DevTools Protocol #5899
Comments
Fix this already!!! |
@mikila85 You are welcome to open a pull request if you need this quickly. You will want to start with the handler for |
Hey, folks. What's the lowest overhead alternative to this in the meantime? Would anyone recommend a workaround? Thanks |
@ThomasGHenry Does |
Thanks, @flotwig. It does not. I'm experiencing this #5876 I'm wondering if anyone recommends a 3rd party option that plays nicely with cypress in the meantime. Cloud-based solutions like Percy and Applitools aren't ideal. Anything else I've found so far uses |
@ThomasGHenry Might have to wait to use With regard to this issue - @jennifer-shehane I think we actually are already taking screenshots using CDP in Chrome and Electron since 3.5.0: cypress/packages/server/lib/browsers/cdp_automation.ts Lines 170 to 177 in 719fd98
So closing this... oops 😅 |
Current behavior:
Cypress screenshot algorithm is complicated and has introduced several challenges.
html
andbody
haveheight: 100%
css style #2681scale: true
are not stitched together as expected, contains black borders / spacings #2348Desired behavior:
Now that #4628 is merged, Cypress has access to Chrome's Debugger Protocol which could be used to take screenshots.
Page.captureScreenshot docs: https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-captureScreenshot
Challenges
Versions
3.7.0
The text was updated successfully, but these errors were encountered: