Bug 10138 - Drawing glitches with Urchin SVG
Summary: Drawing glitches with Urchin SVG
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://69.94.67.101:9999/
Keywords: NeedsReduction
Depends on:
Blocks: 8278
  Show dependency tree / graph
 
Reported: 2006-07-27 22:02 PDT by Alexey Proskuryakov
Modified: 2007-06-12 11:52 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2006-07-27 22:02:10 PDT 
After applying the patch from bug 8278 to make Urchin work with WebKit, I can see many drawing glitches, and some console warnings:

CGContextGetPathBoundingBox: no current point.
...
2006-07-28 08:47:16.261 Safari[295] Warning, no gradient stops, gradient (0x1a9ba120) will be all black!
...
(event handler):Value undefined (result of expression myDoc.getTarget) is not object.

Here's a catch-22: per bug 8278 comment 5, we don't want to enable Urchin SVG from our side, but we also cannot move that issue to Evangelism before we fix the redrawing bugs!
Comment 1 Eric Seidel (no email) 2006-09-24 05:01:16 PDT 
myDoc.getTarget
sounds like they're using adobe getters/setters, which are not supported by Firefox, Safari or Opera.
see http://jwatt.org/svg/authoring/
Comment 2 Eric Seidel (no email) 2007-06-12 11:52:17 PDT 
They detect Adobe SVG viewer and only allow you to view the content if you have it.  We'd have to add some sort of "pretend to have the adobe SVG viewer" debug option for this sort of bug.

I think we're just gonna close this as invalid.