<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 20, 2013 at 6:42 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">I would like to propose a couple of things around browser support and get feedback as to how people feel about them.<div>
<br></div><div>First, I feel we need to finish our support matrix[1]. I would like to propose the following modifications:</div><div><ul><li>Desktop</li><ul><li>IE</li><ul><li>I would like to entertain the idea of going to only IE10 support in the near future. We don't have to do it now but according to Global Stat Counter[2], IE9 is on a steady decline (~5% share) since it is being auto-updated to IE10 (~10% share). What's a good share percentage where we can say we should drop support? 2%? 1%? <1%?</li>
</ul><li>Opera => Current - 1</li></ul><li>Mobile</li><ul><li>Android Browser => Drop 3.2+</li><ul><li>Android folks, where are we on 2.3 usage? Still pretty high?</li></ul><li>iOS Safari</li><ul><li>iOS folks, where are we on 4.3 usage? Can we drop? Especially after release of iOS 7?</li>
</ul></ul></ul></div></div></blockquote><div><br></div><div>See here :-) </div><div><a href="https://dl.dropboxusercontent.com/u/155050/keynote-2013.ios.installed.base.png" target="_blank">https://dl.dropboxusercontent.com/u/155050/keynote-2013.ios.installed.base.png</a><br>
</div><div><br></div><div>And that is BEFORE iOS 7 :-) </div><div><br></div><div>That said, for the native bits, dropped already the support of 4.3 with our 1.1.0 release (see [1]). I'd say doing similar on the JS side of things does make sense</div>
<div><br></div><div><br></div><div>[1] <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-ios-Dropping-support-for-iOS-4-x-td3224.html">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-ios-Dropping-support-for-iOS-4-x-td3224.html</a></div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><ul><ul><li>Windows Phone IE</li><ul><li>Split to WP7.5 and WP8</li><li>Keep 7.5 support or just 8</li><li>WP8 would be IE10</li></ul><li>Mobile Chrome => Current - 1 (Same cycle as Desktop)</li>
<li>Mobile Firefox => Current - 1 (Believe it's same cycle as Desktop)</li></ul></ul><div><br></div></div><div>Second, I would like to expand on an issue we are running into concerning the IE9 support. We have plans to implement multipart upload for Pipeline in the next AGJS release. The only issue is, IE9 does not support XMLHttpRequest2 which means the only way to do REST based file uploads is via an iframe hack which I will not introduce into our code. Until we drop IE9 support, I would like to suggest being able to mark APIs as unsupported in IE9 to keep moving forward with the rest of our modern browsers. Then, once IE9 support is dropped, those notes can be removed.</div>
<div><br></div><div>Thoughts on all points much appreciated.</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>