My favorites | Sign in
Logo
Project hosting will be READ-ONLY Wednesday at 8am PST due to brief network maintenance.
             
New issue | Search
for
| Advanced search | Search tips
Issue 21174: REGRESSION: Paths fail to render in SVG with large viewbox
9 people starred this issue and may be notified of changes. Back to list
 
Reported by chr...@google.com, Sep 05, 2009
Chrome Version       : 4.0.206.1
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 4:
  Firefox 3.x:OK
IE 7:
IE 8:

What steps will reproduce the problem?
1. Open the attached SVG file (badchrome.svg)

What is the expected result?
Should see a parallelogram.

What happens instead?
Shape is invisible.

Please provide any additional information below. Attach a screenshot if
possible.
Recent regression, likely between 4.0.203.2 and 4.0.206.1
Works in Chrome stable

I've also attached a file (goodchrome.svg) where all the viewbox and 
coordinate values are divided by 1000, which still works.
badchrome.svg
284 bytes   Download
goodchrome.svg
295 bytes   Download
Comment 1 by pkasting@chromium.org, Sep 06, 2009
Not sure who the knowledgeable SVG people are
Summary: REGRESSION: Paths fail to render in SVG with large viewbox
Status: Available
Cc: bre...@chromium.org
Labels: -Pri-2 -Area-Misc Pri-1 Area-WebKit Regression Mstone-4
Comment 2 by jon@chromium.org, Sep 08, 2009
(No comment was entered for this change.)
Labels: Skia
Comment 3 by ry4...@gmail.com, Sep 09, 2009
As mentioned in  Issue 21182  this prevents the drawing editor in google docs from working.
Comment 4 by shaiss, Sep 10, 2009
badchrome.svg doesn't work for me either in chromium 4.0.208.0 (25857).
ok in FF 3.5.2
no in Chrome 4.0.206.0
Comment 5 by gacohen, Sep 22, 2009
Ping - with the launch of Chrome Frame, this is going to break drawings within Docs 
for quite a lot of people. It also personally drives me insane since my main 
workstation is Ubuntu. Any way you can bump this one up, or provide assurances the 
issue wont make it out of dev channel?
Comment 6 by mikesmith@chromium.org, Sep 22, 2009
Unrelated to Chrome Frame (entirely distinct from Chrome).
Comment 7 by jon@chromium.org, Sep 22, 2009
We need to fix this as it will be a problem for Chrome Frame users of Google Docs.

Chromium 203.0 was at r24234 and 206.0 was at r25170.  Most likely it was a Skia DEPS 
change.  Skia for 203.0 was at r330.  Skia for 206.0 was at r341.

Look at http://code.google.com/p/skia/updates/list for the list of changes.

Works in Safari 4.0.3 (5531.9), and nightly WebKit r48642.  It also works fine in 
Chrome for Mac 211.2 which does not use Skia.
Status: Assigned
Owner: senorbla...@chromium.org
Cc: anan...@chromium.org dglaz...@chromium.org r...@android.com
Labels: -OS-All OS-Windows ReleaseBlock-Dev
Comment 8 by senorblanco@chromium.org, Sep 23, 2009
(No comment was entered for this change.)
Status: Started
Comment 9 by senorblanco@chromium.org, Sep 23, 2009
I synced to skia r330 (built against a recent chromium, r26834), and the problem is 
still there.  Still investigating.
Comment 10 by senorblanco@chromium.org, Sep 23, 2009
This was introduced in WebKit r47925.  Reverting that change will fix it, but I'll see 
if I can also find a better solution to the problem r47925 was trying to solve.

(CC'ing Roland via email, since he doesn't seem to have a chromium.org account yet.)
Comment 11 by senorblanco@chromium.org, Sep 24, 2009
Submitted https://bugs.webkit.org/show_bug.cgi?id=29696 upstream in WebKit to fix.
Comment 12 by jon@chromium.org, Sep 24, 2009
Looks like this was approved.  We should see a version of 4 with this fix in the dev 
channel next week.
Labels: -ReleaseBlock-Dev
Comment 13 by senorblanco@chromium.org, Sep 25, 2009
Webkit merge has brought this fix it; marking bug as fixed.
Status: Fixed
Comment 14 by mal.chromium, Dec 18, 2009
(No comment was entered for this change.)
Labels: -Area-WebKit Area-Internals Internals-Skia
Sign in to add a comment