Hi Johnny, My understanding is everything should be working in IE 10+, Safari 6+ and mobile safari. If something isn't working then it's probably a bug. We're doing a big push internally to upgrade our testing infrastructure so we can do a better job on cross platform/device testing.
On Mon, Aug 11, 2014 at 6:40 AM, Johnny Larue <[email protected]> wrote: > Hi Rob, > > Thank you and team for Polymer, it's a wonderful thing, as is DART and > Angular! > > I am just leaning Polymer Dart and I plan to adopt these > frameworks/languages for all future HTML 5 development. > > What would help me a lot, and likely a ton of others is to understand > when will the Polymer team complete full Polyfill support for *IE10+,* > Safari 6+, Mobile Safari? > > Currently *IE10+* shows *Limited (Useable)* on *Template*, *Mutation > Observer*, *Custom Elements*. > > This may be the reason that whenever I load up a Polymer based application > it rarely renders in *IE11.09 (Desk Top)* and almost never in the Windows > 8.1 *(Tile View) IE Browser*. > > Do you see *IE10+* getting full PolyFill support anytime soon (perhaps > before end of 2014)? > > Also, what's up with IE, why hasn't MS provided any native support of Web > Components. I thought MS was part of the group pushing the HTML 5 spec? > > Cheers > John > > > > On Saturday, June 28, 2014 7:12:21 PM UTC-4, Rob Dodson wrote: > >> Hey fabrice, as I mentioned over on Youtube >> <https://www.youtube.com/watch?v=HKrYfrAzqFA&google_comment_id=z12cz3qjbzidhdu0h23szp3prmbggnufm>, >> we only support the last two version of each browser. Polymer is a future >> facing library and we would need to significantly increase the size and >> complexity of our polyfill layer if we started reaching back to support >> extremely old legacy browsers. >> >> Btw, you mentioned IE10, we actually do support that one. And there >> aren't many users on older versions of Chrome and Firefox as those browsers >> auto-update. >> >> >> On Sat, Jun 28, 2014 at 3:48 AM, <[email protected]> wrote: >> >>> *Polymer is amazing! (but you probably know this)* >>> Polymer and Material Design was one of the most exciting things I have >>> since in a while! >>> >>> I really liked the idea you could build apps with UI standards for >>> Native device also across the web -- these days so many people think that >>> the web is dead: because Apps are dominating in Mobile and Mobile is >>> quickly dominating the web. >>> I also especially liked transitions/animations which I think is the next >>> paradigm and really can improve UX. The whole Material Design is amazing. >>> Really really really amazing! I found myself watching as many videos as >>> possible on Polymer and Material Design and there are now quite a few! >>> >>> *Browser compatibility: will Polymer be usable in the next 3 years?* >>> But the one big BIG disappointment is browser compatibility. I was >>> disappointed when I say the compatibility guidelines: >>> http://www.polymer-project.org/resources/compatibility.html >>> But somehow I couldn't beleive it and I just hoped it somehow degraded >>> nicely on older browser. I was very disappointed when I found it really >>> doesn't degrade beautifully at all on things like Safari 5 or IE9. It just >>> completely falls appart. Apparently even Android web-view in some cases >>> Polymer will completely break. >>> >>> So everything that was exciting about it especially being cross-device >>> suddenly looked very over-stated at best. I mean we are all still hoping we >>> can finally put IE6 behind us... So Safari 5, IE10, or older versions of >>> Chrome & Firefox: that's at least 3 to 5 years *at best*! >>> >>> I am surprised more efforts were not put to help adopting Polymer by >>> creating a smoother transition by having ways to degrade Polymer >>> beautifully on older browsers. Even if that meant loosing the benefits of >>> Polymer for any of these Browsers. >>> Have I missed something? Is there a way to degrade beautiful Polymer to >>> support the majority of browsers? Will browser compatibility improve: is >>> that somewhere on the near future of the product roadmap? >>> >>> Note: Attaching screenshot of Polymer demo running on Safari >>> >>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Polymer" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/polymer-dev/b7192201-3fd6-48fe-ac20-a042e6f6ee41% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/polymer-dev/b7192201-3fd6-48fe-ac20-a042e6f6ee41%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> Follow Polymer on Google+: plus.google.com/107187849809354688692 > --- > You received this message because you are subscribed to the Google Groups > "Polymer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/polymer-dev/3a70a298-1f9c-4440-a503-2cf981b57d09%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/3a70a298-1f9c-4440-a503-2cf981b57d09%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAJj5OwA%2BoNpkMDuNqWL%2BrDL8TTWjQK55vvCFNNT7_03WOyyzrw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
