Bug 38785
| Summary: | SVG 1.1 2nd edition test suite failures | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | James Robinson <jamesr> |
| Component: | SVG | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | eric, jamesr, krit, rwlbuis, zimmermann |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://samples.msdn.microsoft.com/ietestcenter/#svg11e2 | ||
| Bug Depends on: | 18356 | ||
| Bug Blocks: | |||
James Robinson
We should pass all of these.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Eric Seidel (no email)
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.
Dirk Schulze
(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.
Rob Buis
We pass all three mentioned tests these days (at least on Mac). I think it is best to close this bug.
Alexey Proskuryakov
So why not do that? :)
Rob Buis
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.