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
I found a strange bug which seems to be recent, and I can't explain it. Croppie has been working flawlessly for months and it started doing it maybe weeks ago (can't tell the last time it worked).
If you bind an image to croppie, and then use FileReader to read another one, it seems that the image is being cropped to 1/4 of the top left corner. The base64 image of the reader result is correct, but right after when I load it using croppie result, it's not good anymore.
If I avoir loading the previous image (no bind before the file reader), the image is correct.
Load an image, it should display fine. Uncomment the line 7, Run the script, and load another image. You should see the bug. I tested it on Chrome 63 and Firefox 57.
I would suspect a browser update, but since it is happening on two different browsers...
Hope you can help !
The text was updated successfully, but these errors were encountered:
I found a strange bug which seems to be recent, and I can't explain it. Croppie has been working flawlessly for months and it started doing it maybe weeks ago (can't tell the last time it worked).
If you bind an image to croppie, and then use FileReader to read another one, it seems that the image is being cropped to 1/4 of the top left corner. The base64 image of the reader result is correct, but right after when I load it using croppie result, it's not good anymore.
If I avoir loading the previous image (no bind before the file reader), the image is correct.
Here's a fiddle to test it: https://jsfiddle.net/wcfth1ac/1/
Load an image, it should display fine. Uncomment the line 7, Run the script, and load another image. You should see the bug. I tested it on Chrome 63 and Firefox 57.
I would suspect a browser update, but since it is happening on two different browsers...
Hope you can help !
The text was updated successfully, but these errors were encountered: