matrix-org / matrix-org/matrix.org

docs/developer links to wrong pages on Firefox/Safari

Open
#965 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
616
Forks
463
Avg merge
2d 3h
Merged PRs (30d)
19

Description

**Describe the bug**
On Firefox and Safari the [matrix.org/docs/develop](https://matrix.org/docs/develop/) page looks different than on chromoium and link title don't match the actual link behind it.

**To Reproduce**
Steps to reproduce the behavior:
1. Open [matrix.org/docs/develop](https://matrix.org/docs/develop/) using Firefox or Safari
2. Insect a Link towards the bottom of the page (Use Inspect tool or hover over link and see link preview)
4. Link doesn't lead where the text suggest it does (for example "Types of Bridging" leads to "Introduction")

**Expected behavior**
Link text should match link

**Screenshots**
![image](https://user-images.githubusercontent.com/9203094/111363709-a1a09380-8690-11eb-8f38-fea08a3c89a3.png)
![image](https://user-images.githubusercontent.com/9203094/111364396-72d6ed00-8691-11eb-90d4-804922d6901b.png)

**Desktop (please complete the following information):**
- OS: Ubuntu 20.10 (but also occurs on other systems, for example Android)
- Browser: Firefox (but according to @aaron:raim.ist it also occurs on Safari)
- Version: 86.0

**Smartphone (please complete the following information):**
- Device: Pixel 4a 5G
- OS: Android 11
- Browser: Firefox
- Version: 86.1.1

**Additional context**
This issue does **not** exist on Chrome/Brave

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the matrix.org/docs/develop/ page and reproduce the mismatched link text and targets in Firefox or Safari, then compare the same links in Chrome/Brave. Done means the visible titles and destinations agree across the reported browsers, including the “Types of Bridging” example.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.