38785 2010-05-07 18:28:30 -0700 SVG 1.1 2nd edition test suite failures 2012-06-11 13:02:46 -0700 1 1 1 Unclassified WebKit SVG 528+ (Nightly build) All All RESOLVED FIXED http://samples.msdn.microsoft.com/ietestcenter/#svg11e2 P2 Normal --- 18356 1 jamesr webkit-unassigned eric jamesr krit rwlbuis zimmermann oldest_to_newest 222745 0 jamesr 2010-05-07 18:28:30 -0700 We should pass all of these. 222754 1 eric 2010-05-07 19:03:00 -0700 1. http://samples.msdn.microsoft.com/ietestcenter/svg112/svg/svg/chapter_05.1.svg is likely a <use> implementation detail which WildFox could easily spot. 2. http://samples.msdn.microsoft.com/ietestcenter/svg112/svg/svg/chapter_08.2.svg is that our path parser is more lenient that theirs is (probably than the spec too). Should be an easy fix. Krit or Rob might have a sec to look. 3. http://samples.msdn.microsoft.com/ietestcenter/svg112/svg/svg/chapter_11.4.svg is an obscure detail of how paths are drawn which is currently just showing CG's default behavior. So we may have to write custom code to handle that case since the various GraphicsContext implementations are unlikely following SVG's spec to the letter. 222794 2 krit 2010-05-07 22:02:50 -0700 (In reply to comment #1) > 1. > http://samples.msdn.microsoft.com/ietestcenter/svg112/svg/svg/chapter_05.1.svg > is likely a <use> implementation detail which WildFox could easily spot. > > 2. > http://samples.msdn.microsoft.com/ietestcenter/svg112/svg/svg/chapter_08.2.svg > is that our path parser is more lenient that theirs is (probably than the spec > too). Should be an easy fix. Krit or Rob might have a sec to look. > > 3. > http://samples.msdn.microsoft.com/ietestcenter/svg112/svg/svg/chapter_11.4.svg > is an obscure detail of how paths are drawn which is currently just showing > CG's default behavior. So we may have to write custom code to handle that case > since the various GraphicsContext implementations are unlikely following SVG's > spec to the letter. We should differ between the official (upcoming) SVG test suite and the one of the IE team, or better: open seperate bugs for every issue. 2. is fixed in trunk 3. all platforms fail here. 645424 3 rwlbuis 2012-06-09 15:33:41 -0700 We pass all three mentioned tests these days (at least on Mac). I think it is best to close this bug. 646188 4 ap 2012-06-11 12:58:38 -0700 So why not do that? :) 646189 5 rwlbuis 2012-06-11 13:02:46 -0700 Hi Alexey, (In reply to comment #4) > So why not do that? :) I prefer others confirming my findings :) Thanks for closing all those old bugs.