Skip to content
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

Avoid restoring properties manually that are handled by canvas save stack #2173

Merged
merged 1 commit into from
May 8, 2015
Merged

Avoid restoring properties manually that are handled by canvas save stack #2173

merged 1 commit into from
May 8, 2015

Conversation

asturur
Copy link
Member

@asturur asturur commented May 5, 2015

to be tested with some visual test.

closes #2103

@asturur
Copy link
Member Author

asturur commented May 8, 2015

@kangax to me looks working

image

One property frome object ( shadow or compositing ) does not leak to the next one in stack.

For the cliptTo function i will do a separate PR

kangax added a commit that referenced this pull request May 8, 2015
Avoid restoring properties manually that are handled by canvas save stack
@kangax kangax merged commit 04722f9 into fabricjs:master May 8, 2015
@asturur asturur deleted the object-restore branch May 9, 2015 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

too much canvas restoring in object render
2 participants