Closed Bug 986316 Opened 12 years ago Closed 12 years ago

svg getPointAtLength gives wrong values in version 28.0 Linux

Categories

(Core :: SVG, defect)

28 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: rehan.khalid, Unassigned)

References

()

Details

Attachments

(1 file)

Attached image svgpathpointFinal.jpg
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release) Build ID: 20140317233948 Steps to reproduce: I am working on svg based application. here user can draw different shapes like rect,circle,line etc. I need to convert these shapes into 'path' and then i need all points in the path. My solution is working fine for all shapes, except 'circle'. once user finishes the drawing, i convert the circle to 'path' using 'arc'. and when i try to find path point using 'getPointAtLength' , i get different values in Firefox, which changes the end result. here is the Fiddle Link:- http://jsfiddle.net/xfpDA/ Actual results: My circle is distorted Expected results: it should be a perfect circle. kindly see :- http://stackoverflow.com/questions/22549815/
I can reproduce in Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 But happily, it's already fixed in trunk: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 31.0a1 (2014-03-19) Resolving as WORKSFORME. (Might be useful to find out what fixed it, though.)
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Got pointAtLength issues on OSX, FF 32.0.1 Samples: http://bl.ocks.org/duopixel/3824661 [from ticket https://bugzilla.mozilla.org/show_bug.cgi?id=984796] http://bl.ocks.org/KoGor/8163268 Point coordinates out of line. In firefox 29 it was ok.
Sounds like that merits a new bug, then, given that it worked in Firefox 29. Could you file a new bug? (You're definitely not seeing an instance of *this* bug, since this was about something that was broken in Firefox 28.)
(In reply to Daniel Holbert [:dholbert] from comment #3) > Sounds like that merits a new bug, then, given that it worked in Firefox 29. > Could you file a new bug? > > (You're definitely not seeing an instance of *this* bug, since this was > about something that was broken in Firefox 28.) https://bugzilla.mozilla.org/show_bug.cgi?id=1067244
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: