Improve description of `focus` and `blur` events fired on `window`
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start with the linked Window focus events section and the Window/blur_event and Window/focus_event pages. Compare their current summaries with the cited HTML specification, then update the descriptions so they refer to the window losing or gaining focus and verify the affected documentation pages.
Written by the indexing model from the issue text.
Description
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/Window#focus_events
What specific section or headline is this issue about?
No response
What information was incorrect, unhelpful, or incomplete?
The blur and focus events fired on window are briefly described as:
blur: Fired when an element has lost focus.
focus: Fired when an element has gained focus.
in:
https://developer.mozilla.org/en-US/docs/Web/API/Window#focus_events
https://developer.mozilla.org/en-US/docs/Web/API/Window/blur_event
https://developer.mozilla.org/en-US/docs/Web/API/Window/focus_event
What did you expect to see?
something like:
blur: Fired when the window has lost focus.
focus: Fired when the window has gained focus.
Do you have any supporting links, references, or citations?
Do you have anything more you want to share?
No response
- Dominant language
- Markdown
- Stars
- 11k
- Forks
- 23.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 311
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.
More from mdn/content
-
Content:Learn:CSS good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
area: WebAuthn Content:WebAPI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Content:WebExt
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Content:HTML needs info
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100