feat: add includeTransforms option to measure post-transform rect #109
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.
This PR adds an opt-in includeTransforms option that measures an element's visual (post-transform) bounds using getBoundingClientRect() instead of the layout box. When enabled, it uses a requestAnimationFrame loop to detect transform-only changes (scale, rotate, etc.) that ResizeObserver misses, while pausing automatically when the tab is hidden. The default behavior remains unchanged for backward compatibility, and the feature only runs when explicitly enabled, incurring zero cost for existing users. This addresses issue #100 by enabling accurate measurements for scaled/transformed elements, useful for tooltips, hit detection, and animation synchronization. The implementation includes tests, documentation, and an interactive demo showing a 40×40 box with scale(0.75) reporting ~30×30 in transform-aware mode vs 40×40 in default mode.
Closes #100