javascript-tutorial / javascript-tutorial/en.javascript.info
':hover' popup with links, and no mention of async/await
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 25.5k
- Forks
- 4k
- PR merge metrics
- No merged PRs in 30d
Description
- hovering over 'read this before commenting…' displays a popup with some useful links, but moving the cursor to the popup to attempt to follow a link causes the popup to disappear...making the links useless. Well, it is possible if you carefully move the cursor over the little 'triangle' part of the popup...
- the 'https://javascript.info/try-catch' discussion doesn't comment on its use with async/await, and it's a major use-case since it's the alternative of Promise's 'catch'. Also, this important_warn suggests try/catch isn't going to work with async/await, but that's isn't the case...
- 'name' on anchor elements is deprecated (in favour of 'id'), and the document could use some more 'id's on other parts, like the above 'important_warn'?
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the “read this before commenting…” hover popup and the https://javascript.info/try-catch discussion. Check how the popup links are reached, how async/await is described, and where anchor elements use name instead of id. Done means the popup links remain usable, the async/await explanation is accurate, and the relevant sections have usable ids.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100