2. Describe the buganalyseComplexValue function incorrectly parses matrix3d transform function into a number, leading to incorrect keyframes generation:
// Console warning given by framer motion
Invalid keyframe value for property transform: matrix2.99999d
1. Read the FAQs 👇
2. Describe the bug
analyseComplexValue
function incorrectly parsesmatrix3d
transform function into a number, leading to incorrect keyframes generation:Here: https://github.com/framer/motion/blob/89cf0dcaeebf92583c6c56c26f4550e7e2a45432/packages/framer-motion/src/value/types/complex/index.ts#L41
Workaround: Providing an
initial
transform: matrix3d
to the motion element solves the problem3. IMPORTANT: Provide a CodeSandbox reproduction of the bug
Here is the CodeSandbox reproducing the bug:
A CodeSandbox minimal reproduction will allow us to quickly follow the reproduction steps. Without one, this bug report won't be accepted.
4. Steps to reproduce
Steps to reproduce the behavior:
5. Expected behavior
Parse the
matrix3d
keyword entirely instead of parsing the number3
as an integer6. Video or screenshots
7. Environment details
framer-motion@11.1.9