Open simonkarman opened 4 weeks ago
@mattgperry The issue is now fixed. I'm happy to provide additional testing or troubleshooting if needed before merging.
Quick question about #1877: Was the decision intentional to implement handleChildMotionValue
in HTMLVisualElement
rather than DOMVisualElement
?
Hi @mattgperry, what is the process of getting this PR merged? The pipeline succeeds and there are no conflicts with the main branch. Let me know if you are able to review and approve this. Or let me know if there is someone else I should reach out to. Thanks!
Fixes the issue as described in: https://github.com/framer/motion/issues/2578
Feature was introduced in: https://github.com/framer/motion/pull/1877
Changelog:
motion.text
) now update when given aMotionValue
as children, matching HTML element behavior.