Today I experimented with the effects of using getBoundingClientRect()
on an SVG element that has undergone rotation.
Evaluation:
The outcome revealed:
Chrome, Safari, Opera, and IE seem to calculate the local (untouched) bounding box of the element, then provide the client rect based on that bounding box. This may lead to a client rect larger than expected.
In contrast, Firefox confines the client rect to match the actual element.
Which approach aligns with the specifications?
Personally, I favor the behavior exhibited by Firefox, but (without full grasp of the specifications) suspect that Firefox's divergence could be deemed a glitch.