-
-
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
Viewport Transform and clipping #2629
Comments
i ll check again, i was sure i tested even that. i m on code later, i will check it. |
@asturur don't have a public build of fabric that has your commit yet, but if you setZoom() on the canvas, it should be fairly obvious. For example, when I |
http://jsfiddle.net/asturur/7fsw81mp/7/ link to build file http://www.deltalink.it/andreab/fabric/fabric.js i cannot find the bug. |
@asturur took me a while to figure out, but I re-created the error. The combination of settings that cause it are Fiddle: https://jsfiddle.net/7fsw81mp/8/ |
Going to check now. |
Ok i see the mistake. Should clipping be influenced by canvasZoom? ( i think yes). Same problem for for overlay: shoudl overlay be influenced by canvas zooming? as of now if we are clipping it is not influencede, if we do not clip it is. ( with or without controlsAboveOverlay). Thank for spotting this. |
Ok effectively we the renderAll changes i messed the order of operation. clip. (*just one occurence) I m restoring the normal behaviour with a PR. |
thanks @asturur ! |
I was just testing out the latest build of fabric.js with my application, and ran into a small issue.
Bug is caused by PR: #2580
@asturur Why do we inverse the viewport transform before rendering the controls? This pretty much breaks for everyone who has zoomed the canvas.
The text was updated successfully, but these errors were encountered: