Main site not working on Safari/iPhone/iPad, needs polyfill?
See original GitHub issueThe website at https://ember-intl.github.io/ember-intl/versions/master/docs/quickstart isn’t currently working on the latest Safari 13.1 on macOS, nor on the latest Mobile Safari on iPhone/iPad either.
The error is:
Unhandled Promise Rejection: Error: Intl.RelativeTimeFormat is not available in this environment.
Try polyfilling it using "@formatjs/intl-relativetimeformat"
Should hopefully be an easy fix?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (5 by maintainers)
Top Results From Across the Web
If Safari isn't loading websites or quits on your iPhone, iPad, or ...
If you can't load a website or webpage, or Safari quits unexpectedly, follow these steps.
Read more >How to debug mobile website not working, and/or add ...
I'm testing a website I made in html5/css3 on an old ipod touch 4th gen with the safari browser. It doesn't work on...
Read more >Browser support - Vuetify
Vuetify utilizes features of ES2015/2017 that require the need to use polyfills for Internet Explorer 11 and Safari 9/10.
Read more >primary-navigation's forEach not working on safari ipad ios9
In the Twenty Twenty-One theme, older safari browsers do not support nodelist for forEach they need an Array . Theme: Twenty Twenty-One
Read more >Polyfill.io
Why do I need it? There are lots of differing browsers and browser versions in use throughout the world, each one has a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I believe I’ve addressed everything: https://ember-intl.github.io/ember-intl/versions/master/docs/runtime-requirements
Yup, this was derived from the react-intl API (we share the same foundation and 5.0.0 was bringing the implementations closer together). I missed it in the copy/paste - will fix 😃
Definitely will fix that
Good catch!
I’ll look into this and update react-intl docs as well
Seems reasonable and an easy fix, will add.