29870 2009-09-29 06:49:02 -0700 Actual points string is lost, Webkit normalizes it 2026-04-01 07:55:52 -0700 1 1 1 Unclassified WebKit SVG 528+ (Nightly build) PC OS X 10.5 RESOLVED CONFIGURATION CHANGED P2 Normal --- 0 jeffschiller webkit-unassigned ahmad.saleem792 ap bfulgham karlcow krit rniwa rwlbuis oldest_to_newest 150893 0 40300 jeffschiller 2009-09-29 06:49:02 -0700 Created attachment 40300 Test case revealing the problem. This is similar to other webkit problems where we set a value into the DOM and we can't get that exact value back. Attached is a test case exhibiting the problem. <svg xmlns="http://www.w3.org/2000/svg"> <polyline id="poly" fill="green" /> <script><![CDATA[ var poly = document.getElementById("poly"); var points = "10,10 100,60 10,110"; poly.setAttribute("points", points); if (poly.getAttribute("points") != points) { alert("Pass failed, points attribute equals:\n" + poly.getAttribute("points")); } ]]></script> </svg> The above passes in Firefox and Opera but not in Safari/Chrome because Webkit changes the points string into a space-separate list of numbers. This can be a problem if we need to build up the value of the 'points' attribute and then need to check it at some point. See http://code.google.com/p/svg-edit/issues/detail?id=245 P.S. The 'Version' box in Bugzilla seems to be missing many options (Safari 4?) 404903 1 rwlbuis 2011-05-16 19:37:52 -0700 Seems fixed nowadays. Cheers, Rob. 404963 2 ap 2011-05-17 00:08:56 -0700 Rob, would it make sense to land the test, or do you expect this to be covered already? 405023 3 rwlbuis 2011-05-17 05:29:15 -0700 Hi Alexey, (In reply to comment #2) > Rob, would it make sense to land the test, or do you expect this to be covered already? Good point. I think poly-points-attribute-changes.svg comes really close. It just uses getAttributeNode instead of getAttribute. Assuming both getAttribute and getAttributeNode will use the same internal Attr (which I think is the case) then we do not need the test below. What do you think? Cheers, Rob. 407702 4 krit 2011-05-22 14:10:24 -0700 (In reply to comment #1) > Seems fixed nowadays. > Cheers, > > Rob. The problem here is, that Jeff wants to get the unnormalizd (original string) back. At least if I get it correct. IIRC we don't do this, we just changed our code to comma separated the axis of a point. If you add a space or something else, you can't get the original string back right now. So it is not fixed. 1873785 5 ahmad.saleem792 2022-06-02 21:08:19 -0700 We match with other browser on attached test case but I don't know whether we have test coverage for the following or not. Appreciate if someone can confirm whether it needs test coverage or not. Else it can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks! 1873786 6 ahmad.saleem792 2022-06-02 21:08:23 -0700 We match with other browser on attached test case but I don't know whether we have test coverage for the following or not. Appreciate if someone can confirm whether it needs test coverage or not. Else it can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks! 2195906 7 karlcow 2026-04-01 07:55:52 -0700 Per Ahmad comments. 40300 2009-09-29 06:49:02 -0700 2009-09-29 06:49:02 -0700 Test case revealing the problem. polyline-webkit.svg image/svg+xml 383 jeffschiller PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPgogIDxwb2x5bGluZSBpZD0i cG9seSIgZmlsbD0iZ3JlZW4iIC8+CiAgPHNjcmlwdD48IVtDREFUQVsKICAJdmFyIHBvbHkgPSBk b2N1bWVudC5nZXRFbGVtZW50QnlJZCgicG9seSIpOwogIAl2YXIgcG9pbnRzID0gIjEwLDEwIDEw MCw2MCAxMCwxMTAiOwogIAlwb2x5LnNldEF0dHJpYnV0ZSgicG9pbnRzIiwgcG9pbnRzKTsKICAJ aWYgKHBvbHkuZ2V0QXR0cmlidXRlKCJwb2ludHMiKSAhPSBwb2ludHMpIHsKICAJCWFsZXJ0KCJQ YXNzIGZhaWxlZCwgcG9pbnRzIGF0dHJpYnV0ZSBlcXVhbHM6XG4iICsgcG9seS5nZXRBdHRyaWJ1 dGUoInBvaW50cyIpKTsKICAJfQogIF1dPjwvc2NyaXB0Pgo8L3N2Zz4=