-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
RangeError when visually diffing: The value of "offset" is out of range. #8415
Comments
Duplicate of #2034 |
Well this might be a duplicate but it's broken again and the original thread is locked. Can't bother to submit a proper bug report because I don't know how to reproduce this, it worked fine just a while ago. Maybe I'll just change my selector or something to get over this.
Packages:
EDIT: Ah it appears the bug came from starting to use full-screen mode with Chrome as I run the headed tests. Running headless works fine and headed too when Cypress is windowed. Yet full-screen and perhaps a combination of other variables, I'm downloading files and uploading them which might affect too. Okay, I removed the line where I trigger a download and now it works. So Chrome + headed + full-screen + file download == this bug. I might file a proper bug report but maybe this will help someone. |
Related issue: #5668. As per 5668 I'm raising a new issue in the hope that it is reproducible in this instance.
Current behavior:
When visually diffing an element with Cypress Image Snapshot or cypress-plugin-snapshots using Cypress v4.0.0, or greater, I receive the error "RangeError: The value of "offset" is out of range. It must be >= 0 and <= 22014716. Received -13440" when attempting to compare screenshots.
I do not get this error on version 3.8.3.
Desired behavior:
The plugins work as expected on versions greater than v3.8.3
Test code to reproduce
RangeError: The value of "offset" is out of range. It must be >= 0 and <= 22014716. Received -13440
in the results window.I can paste the full error from the console if necessary, was quite verbose though.
Versions
The text was updated successfully, but these errors were encountered: