On Jan 28, 2014, at 9:40 AM, Karel Piwko <kpiwko(a)redhat.com> wrote:
Given Crypto API is not supported on Android pre 4.0 -
https://issues.jboss.org/browse/AGJS-132, is this right time to drop Android
2.3.3, 3.x stock web browsers?
Or do you want to keep AGJS partially supported on Android 2.3, 3.x?
Most
everything works except that crypto bit, i'd hate to say no support at all, i'm
not really sure what the stats are for 2.3
Thanks,
Karel
On Mon, 20 Jan 2014 11:39:02 -0500
Lucas Holmquist <lholmqui(a)redhat.com> wrote:
> following up from the team meeting, here is the current link to our Browser
> targets
>
>
http://aerogear.org/docs/guides/AeroGearBrowserTargets/
>
> when this was created, i think it was very early on in the project.
>
> the desktop browsers are probably ok at this point, ( i would like to remove
> IE9, though ).
>
> Mobile Browsers i think can be revamped a little, Mobile Safari should
> probably be 6 and 7
>
> we can probably add in Chrome for Android and FireFox for Android
>
>
> WRT the other platforms, i think there is a JIRA to create a Matrix
>
> On Jan 8, 2014, at 5:28 AM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
>
>>>
>>> on this same topic, what % should we be looking at when thinking about
>>> dropping support for other platforms, like android and iOS
>>
>> Don’t think we should have a hard (written in stone) rule, but try and to
>> be pragmatic about what we support.
>>
>> Because if 10% would be the limit for browsers we could drop IE support all
>> together ;) _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev