Bug 20557 – getScreenCTM() returns wrong values

• Status: RESOLVED
• Resolution: FIXED
• Component: SVG

[Tuom Larsen]

For nested SVG, getScreenCTM() returns wrong position values (.e, .f).
Please, see the attachment.

[Tuom Larsen]

Created attachment 23050 [details]
Attachment

[Tuom Larsen]

I should have been a bit more specific, sorry:
The two alerted values should be top and left coordinates of that squate, relative to the browser window.

[Rob Buis]

Created attachment 23626 [details]
First attempt

The patch fixes the testcase. I hope there are no drawback to using the renderer abs pos and not the parents, I cant see any.
Cheers,

Rob.

[Darin Adler]

Comment on attachment 23626 [details]
First attempt

Looks fine. r=me

It'd be a lot better if the test case was a text-only test so it could be used cross platform. You should strive to make new tests text-only whenever possible.

[Tuom Larsen]

(In reply to comment #4)
> 
> It'd be a lot better if the test case was a text-only test so it could be used
> cross platform. You should strive to make new tests text-only whenever
> possible.

I'm sorry, I don't quite understand what do you mean by text only? It is just a text..

[Nikolas Zimmermann]

(In reply to comment #5)
> (In reply to comment #4)
> > 
> > It'd be a lot better if the test case was a text-only test so it could be used
> > cross platform. You should strive to make new tests text-only whenever
> > possible.
> 
> I'm sorry, I don't quite understand what do you mean by text only? It is just a
> text..
Darin, meant a WebKit specific LayoutTest feature "layoutTestController.dumpAsText()". This way the test just logs the actual text output in the test-expected.txt file, instead of the coordinates of the RenderObjects' in the render tree.

Greetings,
Niko
> 

[Rob Buis]

Fixed by r36856.