- From: Jeff Schiller <codedread@gmail.com>
- Date: Tue, 5 Jan 2010 07:45:57 -0600
- To: Erik Dahlstrom <ed@opera.com>
- Cc: www-svg <www-svg@w3.org>, Alex Danilo <alex@abbra.com>
- Message-ID: <da131fde1001050545t4fc26f80l5bc16c9261531ca@mail.gmail.com>
I should have prepended my statement with "if you think the transform attributes have an effect on user space then..." It also seems odd to me that a transform attribute with a scale should have the ability to "reach" in and change the gradient vector's endpoint in that way On Jan 5, 2010 7:32 AM, "Jeff Schiller" <codedread@gmail.com> wrote: The fact that you moved the scale to a parent g with no differences is weird to me. Note that there is already a translate of 100,100 on a parent element that has NO apparent effect on the rects user space On Jan 5, 2010 4:08 AM, "Erik Dahlstrom" <ed@opera.com> wrote: On Tue, 05 Jan 2010 09:18:17 +0100, Alex Danilo <alex@abbra.com> wrote: > --Original Message--: >> ... ... >> >> The spec says userSpaceOnUse "shall represent values in the coordinate >> system that results... > > Just to test for consistency I also verified that moving the transform attribute from the rect ... <?xml version="1.0"?> <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1... <g transform="scale(0.25,1)"> <rect width="400" height="50" fill="url(#g1)" /> <!-- sh... > > <line x1="0" y1="0" x2="400" y2="50" stroke="black"/> > </g> > > <rect y="100" width... > There is clarification for the weird perpendicular behaviour of > the gradients for 'objectBound... > > I agree that it makes sense to make the gradient perpendicular to the gradient vector for both ... /Erik -- Erik Dahlstrom, Core Technology Developer, Opera Software Co-Chair, W3C SVG Working Grou...
Received on Tuesday, 5 January 2010 13:46:31 UTC