Go to mark goes to the wrong location
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Sometimes, go to mark does not works. It goes to an other part of the page.
It still work in some sites.
I don't know what triggers it exactly, I have found the bug in a huge page, with anchor.
To Reproduce
Steps to reproduce the behavior:
- Open this page : https://www.jetbrains.com/help/rider/Reference__Code_Inspections_CSHARP.html
- Scroll down to https://www.jetbrains.com/help/rider/Reference__Code_Inspections_CSHARP.html#CodeRedundancy:~:text=resharper_unused_member_global_highlighting
- Mark it. (
mafor me) - Scroll up with
gg - Go to mark (
'afor me because the default won't work, see my config below)
Result : It goes to https://www.jetbrains.com/help/rider/Reference__Code_Inspections_CSHARP.html#CodeRedundancy
Expected : Should go to the position I've registered
Note that if you skip the scroll up with gg part, so if you are already on the mark, going to the mark will keep you at the same place (working).
Note also that there is an anchor, I don't know if that can help.
My config :
map ' Marks.activateGotoMode
Browser and Vimium version
- Vivaldi : 5.6.2867.62 (Stable channel) (64-bit)
- OS : Windows 10 Version 22H2 (Build 19045.2486)
- Vimium : 1.67.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported behavior on the JetBrains page, using the configured Marks.activateGotoMode entry point and the supplied mark-navigation steps. Compare the saved position with the destination after gg; done means going to the mark returns to the registered text position rather than only the page anchor.
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
- 40/100