-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide clear messaging for unsupported browsers #22
Comments
Is there a user on a platform that can't upgrade to a modern browser? Firefox 14 was released in July of 2012 and given the pace of browser security attacks it is quite dangerous to use any browser that old for day to day browsing. The browser support matrix I've been targeting for sutsis has been the most recent two versions of the five major browsers (Firefox, Chrome, Safari, Opera, and IE). (polymer/Platform was renamed to webcomponentsjs. I can say authoritatively that Polymer is not deprecated) |
2014-11-14 22:14 GMT+03:00 Peter Burns notifications@github.com:
looks like.
well, yes, sorry, that's what i meant, they (you?) just renamed it.
|
2014-11-14 22:29 GMT+03:00 Gleki Arxokuna gleki.is.my.name@gmail.com:
Btw, i tested Firefox 17.0 ESR and it again produces several errors in
|
Support and patches for Firefox 17 ESR ended in December 2013. Firefox 31 ESR is the current extended support release. Did Firefox drop support for the user's platform? |
I think it'd be nice to inject this or similar script to sutsis so that people stop complaining and updating their browsers: Because what happens now is that they say: "It doesn't work". Indeed, they can only see "Loading dictionary ..." message forever. |
+1, good point, I'll roll that in with the next update. |
Looks like Polymer (now deprecated actually) isn't gonna work on Firefox 14.0. It'd be nice to support this browser by either fixing polymer or removing "core-header-panel"
The text was updated successfully, but these errors were encountered: