It's not that simple. The zooming system was probably written long before css transitions existed, and therefore wasn't designed with this use case in mind. S

It's not that simple. The zooming system was probably written long before css transitions existed, and therefore wasn't designed with this use case in mind. So you have one system that handles transforms, and then another that handles UI zoom, and it's unlikely that these systems can even communicate. Yes, in an ideal world, all of your transforming _MATH_ would be in the same place and interoperate. But the reality is that browsers are large, complex systems who's requirements are constantly changing. Do you think these edge cases deserve a massive rewrite? (which in the short term would probably introduce more bugs than it fixes)