-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Bug]: eraser top context cleanup #8601
Comments
I won't be doing backward compat fixes to eraser. #8499 should fix all issues, hopefully. |
Thanks for your prompt reply
do you have a brief overview of this branch fabricjs/fabric.js#ts-eraser-playground ? Best regards |
See the breaking changes issue #8299 |
please try this with the new package erase2d and report there for issue |
Screen_Recording_20230114_111721_Chrome.mp4
CheckList
Version
5.3.0
In What environments are you experiencing the problem?
Chrome
Node Version (if applicable)
None
Link To Reproduction
https://codesandbox.io/s/fabricjs-eraser-forked-3oqi6s?file=/src/index.js&fbclid=IwAR1JsVDwsgXKMMr4xrKxNXmzOzaKC3gPj2Tw_NuBhe--ECX_EiyLq3Zvmqg
Steps To Reproduce
Expected Behavior
once the image fully restored and when the user drag the image to another position it should NOT have any left over under it.
Actual Behavior
when the user restore the image and drag it, it will have most of the times some left over from the previous image.
Error Message & Stack Trace
only js & web on android, and it is happening with many fabric js versions (including 5.3.0) and prior ones.
The text was updated successfully, but these errors were encountered: