User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081211 Shiretoko/3.1b3pre (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081211 Shiretoko/3.1b3pre (.NET CLR 3.5.30729) A skew applied to a path causes the getBoundingClientRect function giving incorrect results. A skewX results in bigger width reported while a skewY results in bigger height reported. Reproducible: Always Steps to Reproduce: apply a skewTransform to a path call getBoundingClientRect Actual Results: A skewX results in bigger width reported while a skewY results in bigger height reported. Expected Results: A correct value

Can you produce a simpler testcase please? One that does not involve dynamically adding SVG data from an XMLHTTPRequest since I can't run that locally. That uses a rect rather than a star as that way it is much easier to see what the bounding box should be if I trace through the code. So ideally just a couple of rect obejects one with a skew transform, the other the getBoundingClientRect of the first set onload.

The actual sample http://go2ghana.net/devel/svg/skewPath.svg points to a single svg where the skwew is set by script runs well locally but with rect makes no sense cos there all works fine: http://go2ghana.net/devel/svg/skewRect.svg

Fixed by check in for bug 465996