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
Actually I'm using the master in above reproduce link.
I want to verify the PR 9801, then I found a new issue.
Scaling flip the Group first
Scaling Flip one child object
The wrong behavior like below gif.
Expected Behavior
The child object inside group can be scaling flip correctly no matter I flip the Group or not.
Actual Behavior
The original issue fixed by PR9801 is gone which is: Don't scaling flip the group, only scaling flip the child object. But it seems the fix is not complete.
Refer to below gif.
Error Message & Stack Trace
No response
The text was updated successfully, but these errors were encountered:
I m not sure i will be able to fix that, because i already tried and fix some other use cases of it.
The fact that the object will flip is something we can't do much about, is how the transformations are calculated and while you could argue that for a simple flip you can calculate when an object should be flipped, that become almost impossible when the transformations stack differently.
Can you please check how this use case was behaving before i merged the fix for your previous issue?
I need to understand if i broke something in case i have to consider reverting
CheckList
Version
6.0.0-rc1
In What environments are you experiencing the problem?
Microsoft Edge
Node Version (if applicable)
None
Link To Reproduction
https://codesandbox.io/p/sandbox/fabric-vanillajs-sandbox-forked-qf599w
Steps To Reproduce
Actually I'm using the master in above reproduce link.
I want to verify the PR 9801, then I found a new issue.
The wrong behavior like below gif.
Expected Behavior
The child object inside group can be scaling flip correctly no matter I flip the Group or not.
Actual Behavior
The original issue fixed by PR9801 is gone which is: Don't scaling flip the group, only scaling flip the child object. But it seems the fix is not complete.
Refer to below gif.
Error Message & Stack Trace
No response
The text was updated successfully, but these errors were encountered: