Closed
Bug 762895
Opened 13 years ago
Closed 13 years ago
firefox 13 is calculation a transformation matrix in SVG differently from firefox 12
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 762411
People
(Reporter: a.simon, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20100101 Firefox/13.0
Build ID: 20120601045813
Steps to reproduce:
- SVG integrated into XHTML statically (not by javascript)
- setting transform attribute
- using javascript SVG API
- calculating transformation matrix by getTransformToElement()
Actual results:
- translation in matrix seem to include viewbox translation of parent element
- see attachment
Expected results:
- translation should correspond to transform attribute
- as in friefox 12 (and internet explorer 9)
- see attachment
Updated•13 years ago
|
Component: Untriaged → SVG
Product: Firefox → Core
QA Contact: untriaged → general
Comment 1•13 years ago
|
||
Can you attach a testcase please?
Comment 2•13 years ago
|
||
Would you be willing to find a regression range? https://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/
Something around February 2012 perhaps
Comment 3•13 years ago
|
||
Probably a duplicate of bug 762411. Impossible to tell without a proper testcase though.
I'm unsure, what you mean by testcase, but I tried to provide something I would use to investigate the problem. Firefox 13 shows "-401,-301" in the end, firefox <=12 (and IE9) "-1,-1" -- always.
The document is served by apache with "Content-Type: application/xhtml+xml; charset=utf-8".
![]() |
||
Updated•13 years ago
|
Attachment #631839 -
Attachment mime type: text/plain → application/xhtml+xml
Comment 5•13 years ago
|
||
Yup, that's a testcase.
Which means that this is the same issue as bug 762411 and the patch in that bug fixes this issue.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
![]() |
||
Comment 6•13 years ago
|
||
a.simon: Thanks for the bug report, and for creating a testcase!
I mentioned it in the bug 762411, but I'll mention it here too: The SVG team could really do with some help catching problems like this _before_ they reach the release builds. We don't seem to have enough people testing SVG before that stage right now. The Beta builds are very stable (get virtually no changes before release), so if you'd be willing to use Beta or Aurora builds for your day-to-day browsing and report any regressions that you notice, that would be a great help. If you're interested, you can find Beta/Aurora builds here:
http://www.mozilla.org/en-US/firefox/channel/
You need to log in
before you can comment on or make changes to this bug.
Description
•