Hydration error when using anchor tag inside of link tag in version 13.0.7

[lforst]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.14.0
      npm: 8.3.1
      Yarn: 1.22.17
      pnpm: 7.6.0
    Relevant packages:
      next: 13.0.7
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "13.0.7", newest: "13.0.7-canary.7".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue

https://github.com/lforst/nextjs-repro

To Reproduce

See readme in repro repo

Describe the Bug

Having an anchor tag

Expected Behavior

Unless I missed something having an anchor tag should still be allowed inside a link tag so the rendering probably should match on client and server.

Which browser are you using? (if relevant)

Chrome 108.0.5359.98

How are you deploying your application? (if relevant)

next build && next start

[lforst]

Ok just found https://nextjs.org/docs/api-reference/next/link#if-the-child-is-a-custom-component-that-wraps-an-a-tag

Was just unexpected that it suddenly throws hydration errors since it started flagging in our integration tests over at https://github.com/getsentry/sentry-javascript

See this as an FYI but feel free to close any time :D

[vercel-release-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.