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
It isn't always appropriate to enable 'allow-external', however, some optimizations can still be made for external links by requesting the browser prefetch the dns records or preconnect to the host. Twitter has enabled such a service while hovering over tweets to external urls.
I would like to propose adding a flag for 'external-preconnect' and appending dns-prefetch or preconnect html tags when a user hovers or begins to click off-domain url.
I know that Chrome, at least, already do similar things automatically, so I'll need to investigate to learn what’s useful and what’s redundant. I’m guessing browsers wouldn’t go farther than prefetching DNS, especially on mobile, so I’m hopeful a JavaScript solution can help via preconnect.
It isn't always appropriate to enable 'allow-external', however, some optimizations can still be made for external links by requesting the browser prefetch the dns records or preconnect to the host. Twitter has enabled such a service while hovering over tweets to external urls.

I would like to propose adding a flag for 'external-preconnect' and appending dns-prefetch or preconnect html tags when a user hovers or begins to click off-domain url.
The text was updated successfully, but these errors were encountered: