https://www.reddit.com/r/webdev/comments/1w5tka1/you_dont_ne...
https://vale.rocks/micros/20260902-1350
https://news.ycombinator.com/item?id=49562996
> initial-scale=1.0 is not useless [1]
[1] https://github.com/mdn/content/issues/45570
In Initial-scale no longer neededmdn
content
Markdown2020–2026
mdn / content
content
The official source for MDN Web Docs content. Home to over 14,000 pages of documentation about HTML, CSS, JS, HTTP, Web APIs, and more.
45Distinct people
51Mentions
0Explicit recommenders
11.1KGitHub stars
What to know before exploring
What it is
The official source for MDN Web Docs content. Home to over 14,000 pages of documentation about HTML, CSS, JS, HTTP, Web APIs, and more.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year51 dated mentions
Observed mentions: 2020-11-03 11:06:07 UTC to 2026-09-25 21:42:17 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 7 | 3 | 4 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 10 | 3 | 7 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 9 | 0 | 9 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 8 | 1 | 7 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Welcome to MDN Web Docs
MDN Web Docs is an open-source, collaborative project that documents web technologies including CSS, HTML, JavaScript, and Web APIs.
Alongside detailed reference documentation, we provide extensive learning resources for students and beginners getting started with web development.
MDN's mission
MDN's mission is to provide a blueprint for a better internet and empower a new generation of developers and content creators to build it.
The strength of MDN Web Docs lies in its vast community of active readers and contributors.
Since 2005, approximately 45,000 contributors have created the documentation we know and love.
Together, contributors have created over 45,000 documents that make up an up-to-date, comprehensive, and free resource for web developers worldwide.
In addition to English-language articles, over 35 volunteers lead translation and localization efforts for Chinese, French, Japanese, Korean, Portuguese, Russian, and Spanish.
Build the site
To set up the site locally, you need to have Node.js installed, which comes bundled with npm.
You can check if these are installed by running the following commands:
node -v
npm -v
After you have installed Node.js, you can install the dependencies using npm install and start the local preview:
npm i
npm start
Once started, a live preview is available at http://localhost:5042/.
Contribute to MDN Web Docs
You can contribute to MDN Web Docs and be a part of our community through content contributions, engineering, or translation work.
The MDN Web Docs project welcomes contributions from everyone who shares our goals and wants to contribute constructively and respectfully within our community.
To find out how to get started, see the CONTRIBUTING.md document in this repository.
By participating in and contributing to our projects and discussions, you acknowledge that you have read and agree to our Code of Conduct, which means adhering to Mozilla's Community Participation Guidelines.
Get in touch
You can communicate with the MDN Web Docs team and community using the communication channels.
Read the full README on GitHubWhat Hacker News says
51 sourcesWhich was premature because most people have missed that initial-scale doesn’t actually default to 1: https://github.com/mdn/content/issues/45570
In Antiquated HTML Snippets and ArtefactsI've just learned that initial-scale was removed from the MDN recommendation only a few days ago... by the submitted article author!
https://github.com/mdn/content/pull/45479
In Antiquated HTML Snippets and Artefacts> That seems rather dodgy.
I fully agree, yet in this particular case it probably holds, with possible exception of 2009 Safari, IIRC [1]. And absolutely agree that defensive @supports is better and more robust way to go. Just aimed to ameliorate the, from my point of view wrong and dangerous pattern using `color: transparent` the easiest possible "drop-in" that would encourage keeping the "normal" `color` intact and only introducing `-webkit-text-fill-color: transparent` on top of that. It seemed like a pattern (lazy) develoers would follow more likely
[1] https://github.com/mdn/content/issues/2638 Made some research while suggesting to promote better approach and point to caveats in the "authoritative" MDN article and partially succeeded. (Sadly, there are `color: transparent`s used in examples there now, but… at least I've tried.)
In CSS properties you should know for better text designsiOS was PWA-only to begin with, but at the same time, OS X didn't support them at all. It was a messy time, but has since changed. [0]
[0] https://github.com/mdn/content/issues/32969
In Building an HTML-first site doubled our users overnightI skimmed the article earlier, but going back and looking, it doesn't appear that the article mentions the spec at all, or links to it. In fact, the first paragraph is literally "People talk about..."
Some help for others to understand the history of this (which apparently Stripe, Paypal, Dwolla, and others use): https://github.com/mdn/content/issues/41497 There are links to the RFC and prior art.
That aside, my first impulse is to say that the server should specify that the key includes a hash of the important parts of the request, checked on receipt, so that only the key itself need be stored. However, FF's implementation apparently(?) adds the header automatically to POST and PATCH if it's not already present, which means that it's not able to comply with such a decision, and the RFC (currently expired) recommends using a UUID, so.
I'm
Read the rest
guessing the original motivation of this is "Browser JS might not be able to send a PUT, or proxies may not handle a PUT correctly".
Correction: the mdn is https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/... and in fact does include an example with fallback sizes. My apologies to the mdn authors – https://github.com/mdn/content/pull/43684
In The end of responsive imagesThe official source for MDN Web Docs content
2 points · Open discussion> Did you manually change the status of those particular things?
No, for the specific issue you mentioned, I found and fixed a logic bug. There are some features/capabilities which are manually assigned in cases where there's no CanIUse or MDN data. (Generally, I'm trying to minimize additions/overrides for maintainability's sake.)
> For instance, I just took another look, and I saw that BackgroundSync is not marked as non-standard. But Mozilla are negative on it: […] And Apple have concerns and have not committed to it either:
This is a very fair point, and again I think you for being very generous with your time and expertise. I've reported this as a bug in the data (https://github.com/mdn/content/issues/41455), and manually overridden the data for now as a workaround.
> Personally, I would remove all the non-standard stuff. Not give a
Read the rest
big list of standard and non-standard stuff mixed together.
I've added a "Hide Experimental" checkbox, which can also be set/shared in a URL property. I'm not yet sure about making that the default, but I hope it's useful!
nit: document.applets is not the same as the <applet> tag.
Note: Support for the <applet> element has been removed by all browsers. Therefore, calling document.applets always returns an empty collection.
https://developer.mozilla.org/en-US/docs/Web/API/Document/ap...
For instance: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...
The <applet> element has been removed (Firefox bug 1279218).
Also see https://github.com/mdn/content/pull/26850 which removed MDN docs for the element a couple years back, citing removals from major browsers.
<font> and <frameset> are still implemented in browsers, though, even if they are fully deprecated and marked by WHATWG as obsolete and non-conforming: https://html.spec.whatwg.org/multipage/obsolete.html#non-con...
In XSLT removal will break multiple government and regulatory sitesIt sounds like this would prevent users from backing up their own data, which is hard with localStorage and sessionStorage, and instead having to rely on the site owner.
However this doesn't go into any detail, so maybe they have some convenient way of being able to access these files in mind, but we'll never know. It reminds me of another shallow dismissal by Mozilla: https://github.com/mdn/content/pull/36294 https://webreflection.medium.com/mdn-doesnt-trust-you-should...
In Pixel 10 PhonesHi, thank you so much for the kind words and thoughtful feedback, I really appreciate it! I’ll be sure to bring this to the team so we can explore how to improve things further.
Would you mind creating an issue for this page using the link below? It helps us track and prioritize updates more effectively: https://github.com/mdn/content/issues/new?template=page-repo...
We actively monitor feedback on GitHub, so if you have more detailed suggestions or broader ideas, feel free to start a conversation on GitHub Discussions → https://github.com/orgs/mdn/discussions
We’d love to hear more from you and identify areas we can improve together.
In Celebrating 20 Years of MDNHi, I'm part of the MDN team. That doesn’t sound quite right, MDN has never replaced example links with AI-generated answers. While we’ve introduced an AI-powered helper to assist with common questions, it’s a supplementary tool, not part of our core documentation experience.
All MDN content remains human-written, maintained by our team and contributors, and based on real browser implementations. You can always view the source and track changes on our GitHub repository for content.
https://github.com/mdn/content
In Celebrating 20 Years of MDNThanks for sharing. The best place to raise issues now is the content repo: https://github.com/mdn/content
In Celebrating 20 Years of MDNThanks so much for sharing this — and for taking the time to raise those issues back then! <3
You're absolutely right that the old `mdn/sprints` repo is no longer the active channel for suggesting or discussing content changes. These days, we encourage folks to file issues directly in the mdn/content¹ GitHub repository. That’s where all our documentation now lives, and it’s actively maintained by MDN staff and contributors.
If you spot inaccuracies, outdated examples, or unclear distinctions on any page, we now have a way to report straight from the page, you can find this at the bottom of every page → "Report a problem with this content." Please feel free to open an issue² or even suggest edits directly via pull request. We also try to prioritize fixes based on how widely used or confusing a topic might be, so calling attention to edge c
Read the rest
ases or under-documented differences is genuinely helpful.
Let me know if you’d like help filing an issue or want to connect with the folks maintaining a specific area of the docs. We’d love to have you involved again!
¹ https://github.com/mdn/content
² https://github.com/mdn/content/issues/new/choose
Showing the 15 most recent of 51 sources. Enable JavaScript to search and browse every indexed mention.