Skip to content

🐛Bug: Internal Documentation and Anchor Links Open in New Tabs #2617

Open

Description

@yashveer-1

Describe the bug

  • Internal documentation links (e.g., /docs/guide) open in a new browser tab instead of navigating in the current tab.
  • In-page anchor links (e.g., #overview) open a new tab instead of scrolling to the corresponding section.
  • Both behaviors appear to originate from the custom anchor renderer in components/StyledMarkdownBlock.tsx.

Steps To Reproduce

  1. Navigate to any documentation page rendered using StyledMarkdownBlock.tsx.
  2. Find and click an internal documentation link (e.g., /docs/guide).
  3. Observe that the link opens in a new browser tab.
  4. Return to the original page.
  5. Click an in-page anchor link (e.g., #overview).
  6. Observe that it also opens in a new browser tab instead of scrolling to the corresponding section.

Expected Behavior

  • Internal documentation links should navigate in the same browser tab.
  • In-page anchor links should scroll to the corresponding section without opening a new tab.
  • External links should continue opening in a new browser tab.

Screenshots

Image Image

Device Information [optional]

- OS:
- Browser:
- version:

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

Activity

  1. added
    🐛 BugIndicates that the issue is a bug or defect.
    Status: TriageThis is the initial status for an issue that requires triage.
    on Oct 31, 2026
  2. mrunalC27 commented on Nov 7, 2026

    @mrunalC27

    I have solved this issue and raised a PR.

  3. Ajaykumar724 commented on Nov 10, 2026

    @Ajaykumar724

    @yashveer-1 Please review #2643 pull request

  4. Ajaykumar724 commented on Nov 10, 2026

    @Ajaykumar724

    Please review my pull request #2643 @vtushar06 and @drishtyraghav0001

  5. yashveer-1 commented on Nov 12, 2026

    @yashveer-1
    Author

    @Ajaykumar724, I was already working on this and was waiting for the approval. Please ask the author first before raising a PR.

  6. Ajaykumar724 commented on Nov 13, 2026

    @Ajaykumar724

    @yashveer-1 Sorry about that! I wasn't aware you were already working on this issue. I should have checked with you first before raising the PR. I didn't intend to duplicate your work. I'll be more careful and coordinate beforehand next time. Thanks for pointing this out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Status: TriageThis is the initial status for an issue that requires triage.🐛 BugIndicates that the issue is a bug or defect.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions