NavigateEvent.sourceElement should mention null for cross-origin initiators
Maintainers usually reply within 1 day
@Stackforge-07 is already working on this.
Since Oct 19, 2026.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Find the MDN documentation page for NavigateEvent.sourceElement in the content repository and compare its description with the linked Window.frameElement and HTMLIFrameElement.contentDocument pages. Check the linked WPT navigation-api/navigate-event/sourceElement-cross-origin.sub.html for the cross-origin case. Done when the page documents that sourceElement is null for an initiator in a cross-origin document.
Written by the indexing model from the issue text.
Description
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/NavigateEvent/sourceElement
What specific section or headline is this issue about?
No response
What information was incorrect, unhelpful, or incomplete?
sourceElement is also null when the initiating element is in a cross-origin document. It would be worth noting that the way Window.frameElement and HTMLIFrameElement.contentDocument do.
What did you expect to see?
See above
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
- Dominant language
- Markdown
- Stars
- 11.1k
- Forks
- 23.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 189
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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
-
ruby-position: Add a Bopomofo (`inter-character`) exampleMay be free again A pull request for this issue was closed without being merged. OpenContent:CSS waiting for implementations
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
mdn/content#46246 · 1 comment ·
Maintainers usually reply within 1 day
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Content:PWA needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mdn/content#45994 · 2 comments ·
Maintainers usually reply within 1 day
-
Add a page for flow-tolerancePossibly taken @BaconMan1168 claimed this 28 days ago. OpenContent:CSS document not written needs BCD update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
WebAuthn Attestation purpose and neccessity is incorrectMay be free again A pull request for this issue was closed without being merged. Openarea: WebAuthn Content:WebAPI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mdn/content#45753 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
sno-ai/sno-station#149 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Git-Hospital/githealthcheck#60 ·
Maintainers usually reply within 1 day
-
docs pkg:core
Difficulty 1/5 Under an hour Newbie friendliness 84/100
pydantic/pydantic-ai#11929 ·
Maintainers usually reply within 1 day
-
[Skill Bug]: entra-agent-id: inaccurate blueprint permission inheritance and parent token sub claimOpenbug entra-agent-id
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/GitHub-Copilot-for-Azure#3467 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
alvarotrigo/fullPage.js#4755 ·