You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can tell, the dns-prefetch is meant to be the fallback in case the preconnect is not supported (as the preconnect would include a DNS resolution). However, the dns-prefetch is mentioned first, which seems odd.
I think this combined preconnect and dns-prefetch resource hint is not always doing what it is supposed to do depending on the browser:
amppackager/transformer/transformers/linktag.go
Line 69 in f1d819c
As far as I can tell, the
dns-prefetch
is meant to be the fallback in case thepreconnect
is not supported (as thepreconnect
would include a DNS resolution). However, thedns-prefetch
is mentioned first, which seems odd.Also, according to web.dev, best practice is to use two separate hints with the
dns-prefetch
as the second hint serving as a fallback, as using a combined hint will break in Safari:https://web.dev/preconnect-and-dns-prefetch/#resolve-domain-name-early-with-reldns-prefetch
The text was updated successfully, but these errors were encountered: