-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Which / are polyfills are needed? #585
Comments
I use es5-shim, es5-sham & addEventListner polyfill and it works for me. |
Hmm ok. The reason for the question is that I don't want to include everything from |
I've made a rapid check on the codebase and seems that addEventListener is the only polyfill needed |
Really? 😳 I expected more. That would be awesome if preact does not require any more polyfills 💃 |
@screendriver hmm - what older browsers? Preact supports IE9+ with no polyfills at all. |
Bam! That's all I wanted to hear 💃 Thank you very much @developit |
Awesome :) For reference, here's the list of browser APIs Preact relies on:
If you use SVG, All of these are actually supported way back beyond IE9, but IE8 and prior includes an issue where you cannot define arbitrary properties on I could definitely see a future where, given that there are hacks to fix #537 already being worked on, Preact would support IE7+ without polyfills. |
👍 That should be either in the README or on https://preactjs.com 😉 |
Totally - we have a browser support page here but it's woefully poor at explaining this. |
Ah I see. Thank you for your help. Hopefully the page will be updated in the future at some point. |
@developit just wanted to check if this is still the case, or if there have been any added since this was discussed? |
@joshua-mason the current version of Preact still works perfectly in IE9. We will likely begin requiring some very minimal polyfills for IE9-11 starting in Preact 11 though. |
Are there any polyfills that are needed for older browser to work with preact?
For example Inferno needs this ones.
The text was updated successfully, but these errors were encountered: