google / google-visualization-issues

288 stars 35 forks source link

Fallback for non-SVG browsers #1355

Open orwant opened 9 years ago

orwant commented 9 years ago
What would you like to see us add to this API?

An automatic fallback for browsers which do not handle SVG. It could be displaying
an image instead of an error.

What component is this issue related to (PieChart, LineChart, DataTable,
Query, etc)?

All components.
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************

Original issue reported on code.google.com by raphael.cohen on 2013-11-03 08:22:35

orwant commented 9 years ago
We currently use VML on versions of IE that do not support SVG. Is there a particular
browser/visualization that you are testing that does not work?

Original issue reported on code.google.com by grabks@google.com on 2013-11-05 14:49:40

orwant commented 9 years ago
Yep, tested it on Android Stock Browser in Android 2.3.7 which definitly doesn't support
SVG. All charts in the Chart Gallery just display "Cannot set property 'overflow' of
null" (except for Table chart which displays Ok). That browser doesn't seem to support
VML either. Maybe I shoud change this feature request to "Fallback for non-SVG and
non-VML browsers" ?

Original issue reported on code.google.com by raphael.cohen on 2013-11-05 15:08:18

orwant commented 9 years ago
I also like what is stated here :

https://developers.google.com/chart/interactive/docs/

"Charts are rendered using HTML5/SVG technology to provide cross-browser compatibility
(including VML for older IE versions) and cross platform portability to iPhones, iPads
and Android. Your users will never have to mess with plugins or any software. If they
have a web browser, they can see your charts."

I wish they could, or maybe just specify it's only for versions gt 2.3 in the docs,
that would save me a lot of time re-developing my app with another chart rendering
engine.

Original issue reported on code.google.com by raphael.cohen on 2013-11-05 15:14:14

orwant commented 9 years ago
In fact, there is already a "Won't fix" bug on the subject (https://code.google.com/p/google-visualization-api-issues/issues/detail?id=935),
I just wanted to try and make it a feature request.

Original issue reported on code.google.com by raphael.cohen on 2013-11-05 15:22:10