IssueTracker

I can not replicate this issue. I am using G1 Running RC30. I have gone to
http://en.wikipedia.org/wiki/File:Bitmap_VS_SVG.svg and other web pages that have embedded svg graphics and
I have found that the browser displays them fine.

What do you get for http://highlandsun.com/hyc/Kazakh/d3/ ? There are 3 SVGs in the
first 2-3 pages, none of them show up on the phone but they all work fine in a
regular browser. Opera on the G1 works too (but Opera doesn't render embedded fonts,
which this page also uses).

We have chosen intentionally to not support SVG in the browser to save space; full SVG adds over 1M to the
webkit image size.

As is described here:
http://googlecode.blogspot.com/2009/10/svg-at-google-and-in-internet-explorer.html

SVG is a really useful technology to have in a mobile browser.  And it is supported
by other mobile devices.

Perhaps the webkit build can be setup so SVG can be added as a downloadable app to
the built in browser.

I would like to use the Google Visualization API on an app that I am building. Is there
some way to do this other than to have the browser support the functionality?  

dacarys: I'm not aware of an interactive alternative to SVG.

We're considering enabling SVG for WebView in a future release, on devices with the memory to support it.

Please enable it by default. Yes, it's easy to enable it by "make ENABLE_SVG=true" and modifying
external/webkit/WebCore/config.h and maybe "external/webkit/WebCore/loader/FrameLoaderClient.h".
However, if it's not enabled by default, I think few devices will support it. And as discussed above, there is no
interactive alternative to SVG.

I hate to add a 'me too' comment, but lack of SVG in the Android browser seems like a big missing feature.  

SVG is part of the HTML5 group of technologies, and as such has wide support across a variety of devices and platforms, including things like the Google Chrome browser, and the iPhone Safari browser.  As linked above Google themselves promotes SVG graphics as excellent technology, being open, cross-platform, easily programmable, and accessible, too, so screen-readers can use them.

Finally, my Google Nexus One has 512 MiB of RAM, and a 1 GHz processor.  Having Android tell me it would be too much work for my hardware to render SVG is hard to accept. It's hard to understand a position which says Android shouldn't be a next-generation web-browser platform.

jonathan.stewart: you may be interested in comment #4 here: http://code.google.com/p/android/issues/detail?id=8202#c4

Can we get consistent status between these two bugs?  Is SVG enabled in the Gingerbread browser now?  Can this bug be closed?

[Comment deleted]

SVG has been enabled in a future release, but not necessarily a release called Gingerbread. Sorry for the confusion.

I'd also like this enabled - the possibilities for producing progressive browser-based content are limited without support for SVG.

Hi,
can you tell which Android release SVG will be supported on and when? SVG coupled with Touch events are great for indoor maps web applications, ... which so far work only on iPhone. In the meantime, I show my customers iPhone and Android HTC Dream side-by-side with crystal clear and interactive SVG on iPhone... and poorly rendered bitmaps on Android. What a pity.

Julien

Jmartin: sorry, this forum is for reporting bugs and requesting features. I cannot comment on Android's internal engineering schedules.

Although it's said that SVG will be enabled by default in next Android release (GingerBread?), we need to test SVG a bit on Android before we have GingerBread. So we tried to enable it. It turned out pretty easily. Tweaked several lines and "make ENABLE_SVG=true ENABLE_SVG_ANIMATION=true", then you got it. Since SVG will be enabled by default, and it's pretty simple,  we won't bother submit the patch. The attached file is patch against AOSP master

Would it be possible to include a replacement version of the browser with SVG support in the marketplace?

It's possible, but it may not be what you thought/wanted. The Android browser consists of three main parts: the Brwoser.apk, Java WebKit binding and related in the android.webkit package,  and the underlying C++ WebKit code. The rendering of SVG is the job of the C++ part. And, unfortunately, I don't think it's possible, or say, legal, to make a package to in the marketplace that can replace those C++ WebKit libs under /system/lib. That is, though what we want to have is a slightly tweaked SVG-enabled Android browser, the resulting package might need to have the 3 parts I mentioned.  

BTW, after I enabled SVG,  the Acid3 results changed from 93/100 to 96/100. However, three of the four remaining failed tests are SVG related.  See the attached file, or check http://www.tandroid.org/enable-android-webkit-svg

It turned that if all SVG code is enabled properly, the browser will pass all SVG tests. The remaining failed one is CSS media related.

https://review.source.android.com/#change,17258

SVG is becoming more and more important for web developers, as it is a popular standard now (Only MS Internet Explorer does not support it yet, but in IE9).

People are relying on it, developers as well as web page visitors, as it is much more performant than the HTML5 Canvas, regarding animation. (See http://www.lutanho.net/svgvml3d/index.html for examples of efficient 3D animations).