Intl polyfill not provided for SamsungBrowser/2.1

I’ve noticed that for both user agents below, we don’t supply the Intl polyfill, even tough it would be needed, as we see Intl is not defined errors from them.

Mozilla/5.0 (Linux; Android 5.0.2; SAMSUNG SM-G850F Build/LRX22G) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/2.1 Chrome/34.0.1847.76 Mobile Safari/537.36

Mozilla/5.0 (Linux; Android 5.0; SAMSUNG SM-G900F Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/2.1 Chrome/34.0.1847.76 Mobile Safari/537.36

[JakeChampion]

The useragent module can now detect Samsung, we need to update the module in our project and add Samsung into the config.json files for the polyfill/s in question.

[triblondon]

@AdaRoseEdwards Problem is Chrome has had Intl since 22 (http://caniuse.com/#search=intl), so maybe the SS fork removed support for Intl, somehow? Anyway basically the solution is simply to choose a sufficiently old version of Chrome.

@torgo do you think we could get some official determination on this from Samsung as a stopgap until we have proper support data? It’s very simple for us to say ‘treat version X of SB as an alias of version Y of Chrome’, and it adds no maintenance overhead, so if there’s a version combination of Chrome and SB where SB’s featureset is a superset of Chrome’s, we can use that for now and the only issue is that we will over-polyfill Samsung.

I really want to fix this as we have a fair number of people reporting it. I’ll put this out as a suggestion:

samsung internet/2.1.0 == chrome/21

WDYT?