Visitar URL original
Remove GH polyfill links to baseline features by Josh-Cena · Pull Request #45958 · mdn/content · GitHub
Skip to content

Remove GH polyfill links to baseline features - #45958

Merged
Josh-Cena merged 1 commit into
mdn:mainfrom
Josh-Cena:rm-polyfill
Oct 10, 2026
Merged

Josh-Cena merged 1 commit into
mdn:mainfrom
Josh-Cena:rm-polyfill

Conversation

@Josh-Cena

@Josh-Cena Josh-Cena commented Oct 3, 2026 •

Copy link
Copy Markdown
Member

We have well-defined policies on whitelisted polyfill sources (core-js and es-shims), but we also have many ad-hoc polyfill links. While we can probably keep the ones that are still useful, the other ones only add noise and maintenance burden.

In an effort to reduce excessive external links, I'm removing these outdated polyfills whose features are already baseline.

@Josh-Cena
Josh-Cena requested review from a team as code owners October 3, 2026 00:57
@Josh-Cena
Josh-Cena requested review from chrisdavidmills, fred-wang and sideshowbarker and removed request for a team October 3, 2026 00:57
@github-actions github-actions Bot added Content:WebAPI Web API docs Content:JS JavaScript docs Content:Media Media docs Content:MathML MathML docs Content:Performance Web performance docs size/m [PR only] 51-500 LoC changed labels Oct 3, 2026
@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor
Preview URLs (14 pages)
External URLs (90)

URL: /en-US/docs/Web/API/Crypto/subtle
Title: Crypto: subtle property


URL: /en-US/docs/Web/API/MediaStream_Recording_API
Title: MediaStream Recording API


URL: /en-US/docs/Web/API/Pointer_events/Pinch_zoom_gestures
Title: Pinch zoom gestures


URL: /en-US/docs/Web/API/ReadableStreamDefaultController
Title: ReadableStreamDefaultController


URL: /en-US/docs/Web/API/Server-sent_events
Title: Server-sent events


URL: /en-US/docs/Web/API/Web_Animations_API/Web_Animations_API_Concepts
Title: Web Animations API Concepts


URL: /en-US/docs/Web/API/Window/structuredClone
Title: Window: structuredClone() method


URL: /en-US/docs/Web/API/WorkerGlobalScope/structuredClone
Title: WorkerGlobalScope: structuredClone() method


URL: /en-US/docs/Web/JavaScript/Reference/Statements/function*
Title: function*


URL: /en-US/docs/Web/MathML/Guides/Authoring
Title: Authoring MathML


URL: /en-US/docs/Web/Media/Guides/Audio_and_video_delivery
Title: Audio and video delivery


URL: /en-US/docs/Web/Performance/Guides/Fundamentals
Title: Performance fundamentals


#### Make events immediate

As old-school, accessibility-aware Web developers we love click events since they also support keyboard input. On mobile devices, these are too slow. You should use {{domxref("Element/touchstart_event", "touchstart")}} and {{domxref("Element/touchend_event", "touchend")}} instead. The reason is that these don't have a delay that makes the interaction with the app appear sluggish. If you test for touch support first, you don't sacrifice accessibility, either. For example, the Financial Times uses a library called [fastclick](https://github.com/ftlabs/fastclick) for that purpose, which is available for you to use.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This hasn't been the case since forever ago

Comment on lines -62 to -64
#### Fallback for browsers without MathML support

It is recommended to provide a fallback mechanism for browsers without MathML support. If your document contains only basic mathematical formulas then a small [mathml.css](https://github.com/fred-wang/mathml.css) stylesheet might be enough. To load it conditionally, just insert one line in your document header:

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I'm not sure if there are still merits in using custom CSS for MathML (probably yes; default MathML looks a bit ugly to me) or even using MathJax/KaTeX (if you value client-side generation, I guess). But they certainly shouldn't be presented as a polyfill mechanism.

@chrisdavidmills chrisdavidmills left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm familiar with many of these features, and I have checked the support status for the ones I'm less familiar with. I think all of these changes made sense.

This is a wide-ranging PR, so I'll approve it, but I think we should leave it open for a couple of days in case anyone else wants to jump in and comment.

@Josh-Cena

Copy link
Copy Markdown
Member Author

OK thanks! As usual I'll hold it until my Friday.

@Josh-Cena
Josh-Cena merged commit 47b1321 into mdn:main Oct 10, 2026
8 checks passed
@Josh-Cena
Josh-Cena deleted the rm-polyfill branch October 10, 2026 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Content:JS JavaScript docs Content:MathML MathML docs Content:Media Media docs Content:Performance Web performance docs Content:WebAPI Web API docs size/m [PR only] 51-500 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants