Skip to content

Conversation

@Josh-Cena
Copy link
Member

@Josh-Cena Josh-Cena commented Oct 7, 2025

Remove a lot of example domains that may happen to be valid, to fix #39865. It is impossible to find all such examples, but I found a good bunch.

@Josh-Cena Josh-Cena requested review from a team as code owners October 7, 2025 21:16
@Josh-Cena Josh-Cena requested review from chrisdavidmills, hamishwillee, rebloor and wbamberg and removed request for a team October 7, 2025 21:16
@github-actions github-actions bot added Content:CSS Cascading Style Sheets docs Content:WebExt WebExtensions docs Content:WebAPI Web API docs Content:JS JavaScript docs Content:Learn Learning area docs Content:HTTP HTTP docs Content:Glossary Glossary entries Content:Security Security docs Content:PWA Progressive Web Apps content labels Oct 7, 2025
@github-actions github-actions bot added the size/m [PR only] 51-500 LoC changed label Oct 7, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 7, 2025

Preview URLs (21 pages)
Flaws (10)

Note! 14 documents with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Learn_web_development/Extensions/Forms/Basic_native_form_controls
Title: Basic native form controls
Flaw count: 2

  • macros:
    • Macro produces link /en-US/docs/Web/CSS/:default which is a redirect
    • Macro produces link /en-US/docs/Web/CSS/:checked which is a redirect

URL: /en-US/docs/Learn_web_development/Extensions/Forms/Sending_and_retrieving_form_data
Title: Sending form data
Flaw count: 1

  • macros:
    • Can't resolve /en-US/curriculum/

URL: /en-US/docs/Web/API/HTMLElement/hidden
Title: HTMLElement: hidden property
Flaw count: 1

  • macros:
    • Macro produces link /en-US/docs/Web/CSS/display which is a redirect

URL: /en-US/docs/Web/CSS/Reference/At-rules/@media/color-index
Title: color-index
Flaw count: 1

  • macros:
    • Macro produces link /en-US/docs/Web/CSS/integer which is a redirect

URL: /en-US/docs/Web/CSS/Reference/At-rules/@media/device-height
Title: device-height
Flaw count: 1

  • macros:
    • Macro produces link /en-US/docs/Web/CSS/length which is a redirect

URL: /en-US/docs/Web/CSS/Reference/At-rules/@media/device-width
Title: device-width
Flaw count: 1

  • macros:
    • Macro produces link /en-US/docs/Web/CSS/length which is a redirect

URL: /en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Allow-Headers
Title: Access-Control-Allow-Headers header
Flaw count: 3

  • unknown:
    • No generic content config found
    • no blog root
    • no blog root

(comment last updated: 2025-11-09 02:29:57)

Comment on lines 42 to 43
1. You visit `a-shopping-site.example`, which uses `ad-tracker.example` to deliver its adverts on the web. `ad-tracker.example` sets a cookie associated with the `ad-tracker.example` domain. While you are on `a-shopping-site.example`, `ad-tracker.example` receives information about the products you browse.
2. You now visit `a-news-site.example` that uses `ad-tracker.example` to deliver adverts. `ad-tracker.example` read its cookie and use the information collected from `a-shopping-site.example` to decide which adverts to display to you.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dotproto any thoughts on this? Does it make the examples to unrealistic?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW I don't much like .example as a TLD, as it is so unexpected (same applies in the XSS guide). But if it's the consensus, I would go along with it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, this was also my initial read here, but I think it's the right call.

@github-actions github-actions bot added the merge conflicts 🚧 [PR only] label Nov 4, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

This pull request has merge conflicts that must be resolved before it can be merged.

@Josh-Cena Josh-Cena requested review from a team as code owners November 7, 2025 19:26
@Josh-Cena Josh-Cena requested review from bsmth and willdurand and removed request for a team November 7, 2025 19:26
@github-actions github-actions bot removed the merge conflicts 🚧 [PR only] label Nov 7, 2025
@github-actions github-actions bot removed the Content:Security Security docs label Nov 7, 2025
@Josh-Cena
Copy link
Member Author

Hi everyone! Since we can't agree on using the .example TLD I'm removing it from this PR, and only working on the cases where the domain name itself has no meaning and can be replaced with example.com.

@Josh-Cena Josh-Cena removed request for a team and willdurand November 7, 2025 19:35
@Josh-Cena Josh-Cena changed the title Only use *.example and example.com as example domains Only use example.com as example domain Nov 9, 2025
@Josh-Cena Josh-Cena merged commit 6ef7bc0 into mdn:main Nov 9, 2025
8 checks passed
@Josh-Cena Josh-Cena deleted the example-domain branch November 9, 2025 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Content:CSS Cascading Style Sheets docs Content:Glossary Glossary entries Content:HTTP HTTP docs Content:JS JavaScript docs Content:Learn Learning area docs Content:PWA Progressive Web Apps content Content:WebAPI Web API docs Content:WebExt WebExtensions docs size/m [PR only] 51-500 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

example.com is a better choice for an example domain

4 participants