Closed
Bug 272630
Opened 20 years ago
Closed 19 years ago
On 'svg' elements getScreenCTM behaves differently to other implementations
Categories
(Core :: SVG, defect)
Core
SVG
Tracking
()
RESOLVED
FIXED
People
(Reporter: jwatt, Assigned: jwatt)
Details
(Keywords: fixed1.8, Whiteboard: SVGWG)
Attachments
(6 files, 2 obsolete files)
604 bytes,
image/svg+xml
|
Details | |
593 bytes,
image/svg+xml
|
Details | |
622 bytes,
image/svg+xml
|
Details | |
961 bytes,
image/svg+xml
|
Details | |
30.03 KB,
patch
|
tor
:
review+
tor
:
superreview+
asa
:
approval1.8b5+
|
Details | Diff | Splinter Review |
771 bytes,
image/svg+xml
|
Details |
Bug go make sure I follow up on this: http://lists.w3.org/Archives/Public/www-svg/2004Sep/0066.html
Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•20 years ago
|
||
Okay, this is how I think we should behave, which happens to be the way the ASV6 alpha behaves (bar a bug I found in it). Certainly we should be accounting for the transform due to the x and y attributes. I also think we should be appending the viewBox to viewport transform. There is a note in the source saying that if we do that for nsSVGSVGElement we need to modify nsSVGGraphicsElement::GetCTM, but I don't see why. The only time nsSVGGraphicElement::GetCTM effects nsSVGSVGElement::GetCTM or visa versa is in nsSVGSVGElement::GetCTM.
Attachment #170818 -
Flags: review?(tor)
Assignee | ||
Comment 2•20 years ago
|
||
Comment on attachment 170818 [details] [diff] [review] patch cancelling review request since we can't just use x and y (they are ignored on outer <svg> elements)
Attachment #170818 -
Flags: review?(tor)
Assignee | ||
Comment 3•20 years ago
|
||
I've followed up this issue in the thread beginning at http://lists.w3.org/Archives/Public/www-svg/2005Jan/thread.html#15
Assignee | ||
Updated•20 years ago
|
Whiteboard: SVGWG
Assignee | ||
Comment 4•20 years ago
|
||
CC'ing Chris and Dean. I haven't recieved any confirmation from the SVG WG that this is an issue, or alternatively an explaination of why it isn't an issue. If it is agreed that there is ambiguity here, can we have some clarification on what the correct behaviour is please?
Assignee | ||
Updated•19 years ago
|
Summary: Make getCTM() behave correctly → On 'svg' elements getScreenCTM behaves differently to other implementations
Assignee | ||
Comment 5•19 years ago
|
||
Attachment #170818 -
Attachment is obsolete: true
Assignee | ||
Comment 6•19 years ago
|
||
Assignee | ||
Comment 7•19 years ago
|
||
Assignee | ||
Comment 8•19 years ago
|
||
Assignee | ||
Comment 9•19 years ago
|
||
The changes to GetScreenCTM are "finished" and pass all the tests I just attached. GetCTM and GetTransformToElement still need work.
Assignee | ||
Comment 10•19 years ago
|
||
This is as far as I'm going with this tonight. I'm fairly confident this is correct, but I'll do some more testing tomorrow.
Attachment #197726 -
Attachment is obsolete: true
Attachment #197790 -
Flags: superreview?(tor)
Attachment #197790 -
Flags: review?(tor)
Assignee | ||
Comment 11•19 years ago
|
||
Attachment #197790 -
Flags: superreview?(tor)
Attachment #197790 -
Flags: superreview+
Attachment #197790 -
Flags: review?(tor)
Attachment #197790 -
Flags: review+
Assignee | ||
Updated•19 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 12•19 years ago
|
||
Comment on attachment 197790 [details] [diff] [review] probably finished patch Requesting approval. This bug fixes a high visibility conformance issue. The modified methods are not run by our internal code, they are only used by content. The risk from this change should be very low.
Attachment #197790 -
Flags: approval1.8b5?
Comment 13•19 years ago
|
||
Comment on attachment 197790 [details] [diff] [review] probably finished patch last day for non-critical changes.
Attachment #197790 -
Flags: approval1.8b5? → approval1.8b5+
You need to log in
before you can comment on or make changes to this bug.
Description
•