-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Should not try to read optional props from a document fragment #1139
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
Comments
Hmm, looks like all props should be just skipped in this case. But under what situation would a fragment be passed to the instance? |
Probably not useful for practical usage, but I was trying to get Vue working again in the framework benchmark :) |
Hah, that seems to be a lot faster than the old version... |
Yeah :D |
Well, the bottleneck for style-attribute-based animations is almost never the framework, but the properties you are animating ;) |
fiddle: http://jsfiddle.net/o65b85e1/1/
results in:
The text was updated successfully, but these errors were encountered: