Also polyfill Android

[jonathantneal]

Also polyfill Android

[jonathantneal]

I could cut a release that utilizes https://code.google.com/p/canvg/ based on this post from 2012.

Related; what are the other methods? I will link to them in the README.

[edge0703]

That would be great. Alas I never thought much about SVG polyfills and have no experience on this topic. However should I help yiu to search for alternatives?

[jonathantneal]

@edge0703, Yes, thank you, and please do. I shift back and forth between a few projects. Also, it would be useful to know which version of Android things started working in.

[Rowno]

I have confirmed that the Android 4.0-4.3 stock browsers don't support external SVG spritemaps and that the svg4everybody polyfill makes them work fine when activated.

Android 2.3 doesn't support inline SVG at all and in Android 4.4 Google Chrome is the new stock browser so external SVG spritemaps work fine there.

[jonathantneal]

Great info. This should be added to the README, too!

[Rowno]

More importantly, a detect for Android 4.0-4.3 should be added. 😉

[jonathantneal]

@Rowno, how is this working on your end?

[Rowno]

I'm pretty sure this will execute on Chrome for Android as well when it doesn't need it because it's user agent is:

Mozilla/5.0 (Linux; Android 4.0.4; Galaxy Nexus Build/IMM76B)
AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.133 Mobile
Safari/535.19

[Rowno]

Firefox Mobile and Opera Mobile will get targeted by the current regex as well. (both support external SVG spritemaps)

[jonathantneal]

I’m sorry. User Agent strings are terrible things. Is there something unique about the default browser?

[Rowno]

Not sure, looks like you'll need to check the Android version and the AppleWebKit version unfortunately: https://stackoverflow.com/questions/14403766/how-to-detect-the-stock-android-browser

[jonathantneal]

Or the absence of Chrome or Firefox?

[Rowno]

That wouldn't be very safe, there's a lot of other Android browsers (including Opera).

[Rowno]

I think checking the webkit version is probably the safest and most future proof. Since technically it's that webkit version that's lacking support.

[jonathantneal]

Very well. Sorry, I don’t have multiple Android devices to test.

[jonathantneal]

With the latest update, are we good, @Rowno?

[Rowno]

The only thing is that this will target all old Webkits (including Safari desktop and mobile) even if they don't support inline SVG, which may be a problem? If so, you could check the Android version and the Webkit version.

[Rowno]

Or add an inline SVG feature detect for when Webkit is detected.

[edge0703]

Is it already supposed to work in Android? Tried it now and still no display of external SVGs.

[Rowno]

Is it already supposed to work in Android? Tried it now and still no display of external SVGs.

Yes it does (Android 4.0-4.3).

[jonathantneal]

@edge0703, which version of Android are you testing?

[edge0703]

I tried it on Browserstack with several versions of Android. Didn't work on any. But I didn't try it on an actual device. Maybe I will do that now.

[Rowno]

I was testing on Browserstack and it was working fine.

[edge0703]

You were right, it works. Just tried it on my Nexus 4. Don’t know why it didn’t work in Browserstack before.

Am 16.06.2014 um 08:53 schrieb Roland Warmerdam [email protected]:

I was testing on Browserstack and it was working fine.

—
Reply to this email directly or view it on GitHub.

[Rowno]

FYI, svg4everybody is executing on Chrome now because /Trident\/[567]\b|/.test(navigator.userAgent) is returning true. :(

[jonathantneal]

Double check that, @Rowno ;)