Safari support through fallback?

Question

Safari support through fallback?

Opened this issue 4 years ago · 7 comments

Incompatible browsers
Safari 13.0 has support for <link rel="prefetch"> but it’s disabled by default. Hopefully it will be enabled in March.

Is that still true?

Answer 1 · 2020-01-31T11:27:29.000Z

And with "March" you intend March of which year?

Answer 2 · 2020-01-31T11:52:20.000Z

I can see from here it's true https://caniuse.com/#feat=link-rel-prefetch
So you mean that instant page doesn't have any effect on Safari?

Answer 3 · 2020-02-01T13:11:15.000Z

March of this year. Though it’s February and Apple has yet to enable it by default. Maybe for September then…

In the mean time I plan to make a reboot of InstantClick renamed “instant.page extra” that will work in Safari starting from 12.1.

Answer 4 · 2020-02-03T20:14:37.000Z

I’m getting confused with all of those names and versions. Now I’m thinking to use QuickLink but only on the mobile version of the websites.

I liked the idea behind InstantPage v3. Why don’t you make only one script (meaning name it in a single way) that works everywhere?

Answer 5 · 2020-02-05T09:22:06.000Z

instant.page’s way of preloading doesn’t work in Safari. InstantClick’s way of preloading works nearly everywhere but it transforms a site into an SPA, so it needs additional work to function correctly. quicklink’s way of preloading in Safari doesn’t work if you don’t have cache headers, most pages don’t have those so I don’t include a fallback like they do.

Answer 6 · 2020-02-06T06:47:29.000Z

We have cache headers and the vast majority of our user base is on Safari, so using QuickLink on mobile is probably a good idea. Thanks

Answer 7 · 2023-04-18T09:32:03.000Z

Given that Safari still doesn’t ship prefetch by default, I plan to reevaluate the fallback options for it.