docs(animation): add MAX_SAFE_INTEGER warning for large input edge case #3231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does
This PR adds a short comment to the JavaScript example in the animation guide, warning users about potential issues with large input values exceeding
Number.MAX_SAFE_INTEGER
.Why
The current example uses tweening to animate a number input. However, if the input exceeds 2^53 - 1 (
9007199254740991
), JavaScript may no longer represent it precisely due to floating-point limitations. This note aims to clarify that it's an edge case and not an issue with the example itself.Changes
watch
block in thegsap
example warning aboutNumber.MAX_SAFE_INTEGER
Additional Notes