Skip to content
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

Add note about dns-prefetch as fallback #30385

Merged
merged 3 commits into from
Feb 6, 2022
Merged

Add note about dns-prefetch as fallback #30385

merged 3 commits into from
Feb 6, 2022

Conversation

krychaxp
Copy link
Contributor

Bug

  • Related issues linked using fixes #number
  • Integration tests added
  • Errors have helpful link attached, see contributing.md

Feature

  • Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
  • Related issues linked using fixes #number
  • Integration tests added
  • Documentation added
  • Telemetry added. In case of a feature if it's used or not.
  • Errors have helpful link attached, see contributing.md

Documentation / Examples

  • Make sure the linting passes by running yarn lint

@janicklas-ralph
Copy link
Contributor

I don't think this is the official recommendation. Do you have any tests to show how this change is useful?

Copy link
Member

@ijjk ijjk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, it looks like using dns-prefetch and preconnect on the same link tag is advised against as this causes a bug in Safari where using both causes the preconnect to be cancelled (related post here).

It does look like browser support is better for dns-prefetch so we could add a note mentioning a separate link tag with dns-prefetch can be added as a backup for browsers that don't support preconnect.

We can also add the above article to the useful links for a reference.

@ijjk ijjk changed the title Add also dns-prefetch Add note about dns-prefetch as fallback Feb 6, 2022
@kodiakhq kodiakhq bot merged commit 3055a82 into vercel:canary Feb 6, 2022
natew pushed a commit to natew/next.js that referenced this pull request Feb 16, 2022
## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `yarn lint`


Co-authored-by: JJ Kasper <[email protected]>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 8, 2022
@krychaxp krychaxp deleted the patch-1 branch October 29, 2023 04:30
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants