Remove polyfills natively supported across the browser support matrix - #127
Draft
mattcosta7 with Copilot wants to merge 2 commits into
Draft
mattcosta7 with Copilot wants to merge 2 commits into
mattcosta7 with Copilot wants to merge 2 commits into
Conversation
Co-authored-by: mattcosta7 <8616962+mattcosta7@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove unnecessary browser polyfills based on Browserslist policy
Remove polyfills natively supported across the browser support matrix
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every polyfill in this package except
requestIdleCallbackand the Invoker Commands API is now natively available in all browsers selected by our Browserslist policy (last 10 Chrome/Edge/Firefox versions,last 3 Safari major versions,Firefox ESR). This drops ~9 modules and one dependency from the shipped bundle.src/index.tsThe registry retains only the two polyfills still doing work — Safari lacks
requestIdleCallback, and Firefox ESR / older Safari majors lackcommand/commandfor:baseSupportis intentionally unchanged: its checks are independent feature detection for the support floor, not mirrors of the polyfill registry.Deleted sources and tests
clipboarditem,element-checkvisibility,navigator-clipboard,object-groupby,map-groupby,promise-try,promise-withResolvers,iterator-helpers,set-methods— plus their counterparts intest/.Dependencies
@oddbird/popover-polyfillremoved vianpm uninstall(package.json+package-lock.json).invokers-polyfillstays.Support matrix docs
docs/index.htmlresolves each row'sdata-polyfillkey against the exported registry, so rows for now-absent keys would render as unsupported. Removed the rows forclipboardItem,elementCheckVisibility,navigatorClipboard, and bothpopoverentries.Note for reviewers
The
beforetoggle on Dialogrow referencesdata-polyfill="dialogToggleEvents", which was already missing from the registry before this change. Left as-is to keep the diff scoped — worth a follow-up.