"f" command doesn't detect <area> elements (depending on position)
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
The extension doesn't always display clickable area elements inside maps.
Seems to be linked to scroll position inside the page.
To reproduce:
- Go to: https://www.w3schools.com/html/html_images_imagemap.asp
- Press f, see how the three elements in the picture are detected correctly.
- Scroll down and press f again. As you go down, some elements disappear, until none is displayed.
Tested on Vimium 1.66 on both Chrome 75.0.3770.142 and Firefox 81.0.1.
OS: Windows 10 Pro 64-bit 19041
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 issue at the W3Schools image-map URL by pressing f before and after scrolling. Start by tracing the code that detects clickable elements for the f command, focusing on area elements and scroll position; done means all three map elements remain detected after scrolling.
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
- 45/100