{ "version": "https://jsonfeed.org/version/1", "title": "mdn/browser-compat-data update data", "home_page_url": "https://azu.github.io/github-search-rss/mdn-browser-compat-data.json", "feed_url": "https://azu.github.io/github-search-rss/mdn-browser-compat-data.json", "description": "mdn/browser-compat-data update data on GitHub", "items": [ { "content_html": "\"\"/
\n

Summary

\n

Fixes a couple of errors reported with #29189.

\n\n

Test results and supporting details

\n\n\n

Related issues

\n\n", "url": "https://github.com/mdn/browser-compat-data/pull/29194", "title": "Fix errors in previous base-select PR", "date_modified": "2026-03-05T19:55:04.000Z", "date_published": "2026-03-05T18:12:19.000Z", "author": { "name": "chrisdavidmills", "url": "https://github.com/chrisdavidmills" } }, { "content_html": "\"\"/

Summary

\n\n

Test results and supporting details

\n\n

Related issues

\n", "url": "https://github.com/mdn/browser-compat-data/pull/29186", "title": "added firefox support with flag for attr(type())", "date_modified": "2026-03-05T11:22:09.000Z", "date_published": "2026-03-04T17:02:58.000Z", "author": { "name": "dletorey", "url": "https://github.com/dletorey" } }, { "content_html": "\"\"/

FF149 adds support for HTMLElement.captureStream() in https://bugzilla.mozilla.org/show_bug.cgi?id=2017708 - and this was recoreded in #29135.

\n

Previously only a non-standards-compliant version mozCaptureSttream() was defined. The docs contained notes about the compliance issues. This attempts to move those to BCD, where they belong.

\n

Related work for this can be tracked in mdn/content#43215

", "url": "https://github.com/mdn/browser-compat-data/pull/29165", "title": "HTMLMediaElement.captureStream - add notes", "date_modified": "2026-03-03T06:41:38.000Z", "date_published": "2026-03-03T06:40:59.000Z", "author": { "name": "hamishwillee", "url": "https://github.com/hamishwillee" } }, { "content_html": "\"\"/

Summary

\n

Updates the Safari support statements for the loading/loadingdone/loadingend events for FontFaceSet: The event handlers are supported, but the events never fire.

\n

Test results and supporting details

\n\n

Related issues

\n

Fixes #29035.

", "url": "https://github.com/mdn/browser-compat-data/pull/29066", "title": "Safari only partially supports `FontFaceSet` loading events", "date_modified": "2026-02-23T12:09:25.000Z", "date_published": "2026-02-17T20:26:00.000Z", "author": { "name": "caugner", "url": "https://github.com/caugner" } }, { "content_html": "\"\"/
\n

Summary

\n\n

Chrome 146 adds support for scroll-triggered animations; see https://chromestatus.com/feature/5181996801982464.

\n

The latest Chrome collector PR has added BCD for several of the related features; my PR adds a few more, namely the <animation-action> data type, and the related range properties, which are supported but currently under an old name.

\n

Test results and supporting details

\n\n\n

Related issues

\n\n", "url": "https://github.com/mdn/browser-compat-data/pull/29034", "title": "Chrome 146 scroll-triggered animations", "date_modified": "2026-03-05T12:08:42.000Z", "date_published": "2026-02-12T15:28:11.000Z", "author": { "name": "chrisdavidmills", "url": "https://github.com/chrisdavidmills" } }, { "content_html": "\"\"/

Summary

\n

Address is the dev-doc-needed requirements of

\n\n

Related issues

\n

Related content changes in mdn/content#42997

", "url": "https://github.com/mdn/browser-compat-data/pull/28964", "title": "Bug-2012727 action.isEnabled updated properties info", "date_modified": "2026-02-26T10:35:08.000Z", "date_published": "2026-02-03T17:37:22.000Z", "author": { "name": "rebloor", "url": "https://github.com/rebloor" } }, { "content_html": "\"\"/
\n

Summary

\n

Chrome 144 supports the ::search-text pseudo-element, which allows custom styling to be applied to browser search results; see https://chromestatus.com/feature/5195073796177920.

\n

We already have BCD for ::search-text, however, you can combine ::search-text with the :current pseudo-class to style the currently-highlighted search term on the page. This currently doesn't have any BCD, so I am using this PR to add :current BCD.

\n

I'm assuming it makes sense to put Chrome 144 down for this as well, as previously, there was no context in which :current was supported. However, you might have other opinions on this.

\n

I also thought about putting \"partial_implementation\": \"true\" for this, but then again, :current is fully supported in the context it is supported in. It just isn't supported in other contexts.

\n\n

Test results and supporting details

\n\n\n

Related issues

\n\n", "url": "https://github.com/mdn/browser-compat-data/pull/28882", "title": "Chrome 144 :current support", "date_modified": "2026-02-03T12:43:28.000Z", "date_published": "2026-01-21T18:28:23.000Z", "author": { "name": "chrisdavidmills", "url": "https://github.com/chrisdavidmills" } }, { "content_html": "\"\"/

Summary

\n

There is updates to add details to cover Safari support for documentId and parentDocumentId. More information on changes see the related content PR. (TBC)

\n

Related issues

\n

Fixes #28341
\nRelated content changes in (TBC)

", "url": "https://github.com/mdn/browser-compat-data/pull/28790", "title": "Issue-28341 webextension.api documentId and parentDocumentId updates", "date_modified": "2026-01-15T15:37:17.000Z", "date_published": "2026-01-09T18:11:24.000Z", "author": { "name": "rebloor", "url": "https://github.com/rebloor" } }, { "content_html": "\"\"/

Summary

\n\n

Test Results and Supporting Details

\n\n", "url": "https://github.com/mdn/browser-compat-data/pull/28503", "title": "Safari 26 removed ``", "date_modified": "2026-02-17T12:20:30.000Z", "date_published": "2025-11-21T20:01:18.000Z", "author": { "name": "andesco", "url": "https://github.com/andesco" } }, { "content_html": "\"\"/
\n

Summary

\n\n

Google Chrome deprecated (Browsing) Topics API.

\n

Test results and supporting details

\n

Google Chrome deprecated (Browsing) Topics API, so mark the following MDN features deprecated:

\n\n

Source:
\nhttps://groups.google.com/a/chromium.org/g/blink-dev/c/_R85yctz4Rs

\n\n\n

Related issues

\n

Tracking MDN issue #28417.

\n\n", "url": "https://github.com/mdn/browser-compat-data/pull/28418", "title": "Deprecate Google Privacy Sandbox (Browsing) Topics API", "date_modified": "2025-11-18T10:41:41.000Z", "date_published": "2025-11-08T12:53:14.000Z", "author": { "name": "bershanskiy", "url": "https://github.com/bershanskiy" } }, { "content_html": "\"\"/

Summary

\n

Unmarks Firefox as partial for ::highlight CSS Selector, and splits up the existing notes, adding bug links.

\n

Test results and supporting details

\n

I challenge the following requirement for partial implementation:

\n
\n

The browser's support has a demonstrable negative impact on web developers.

\n
\n

Related issues

\n

Related: #28374

", "url": "https://github.com/mdn/browser-compat-data/pull/28375", "title": "Unmark Firefox as partial for `::highlight` CSS selector", "date_modified": "2026-01-09T14:46:13.000Z", "date_published": "2025-11-04T12:12:56.000Z", "author": { "name": "caugner", "url": "https://github.com/caugner" } }, { "content_html": "\"\"/
\n

Summary

\n

Chromium browsers support User-Agent reduction, which means that features such as the User-Agent HTTP header provide less-specific information in an effort to reduce their effectiveness for fingerprinting/tracking.

\n

This PR adds data points covering User-Agent reduction to relevant web platform features that I know to be affected by the change.

\n

Compat data sources:

\n\n

Another question for Mike: For all of these data points, I used https://wicg.github.io/ua-client-hints/#user-agent as the spec_url. Are there better spec URLs we can point to for these individual features?

\n

This PR is part of the final set of privacy sandbox information to be added to MDN. Much of it is being removed, but this feature is stable and will be kept, so it should be added.

\n\n

Test results and supporting details

\n\n\n

Related issues

\n\n", "url": "https://github.com/mdn/browser-compat-data/pull/28275", "title": "Chrome 110 applies User-Agent reduction to Navigator properties + `User-Agent` header", "date_modified": "2025-11-07T14:33:52.000Z", "date_published": "2025-10-23T15:21:08.000Z", "author": { "name": "chrisdavidmills", "url": "https://github.com/chrisdavidmills" } }, { "content_html": "\"\"/
", "url": "https://github.com/mdn/browser-compat-data/pull/27904", "title": "Add CSS caret property (WIP - awaiting browser support)", "date_modified": "2025-09-16T16:55:16.000Z", "date_published": "2025-09-16T16:54:30.000Z", "author": { "name": "yashrajbharti", "url": "https://github.com/yashrajbharti" } }, { "content_html": "\"\"/

Summary

\n

Safari 14.1 and newer displays a time picker for datetime-local.
\ndatetime-local was not working correctly in one of the Safari tech previews but was fixed before the final 14.1 release.

\n

Test results and supporting details

\n

See the Safari 14.1 release note (https://developer.apple.com/documentation/safari-release-notes/safari-14_1-release-notes)

\n
\n

Added support for HTML date, time, and datetime-local input types in macOS, enabling date and time controls in forms.

\n
\n

This is confirmed by the according issue (comment 27): https://bugs.webkit.org/show_bug.cgi?id=214946#c27

\n

More confirmations:

\n\n

A jsfiddle to test yourself: https://jsfiddle.net/8gw2yk5e/

\n

Related issues

\n", "url": "https://github.com/mdn/browser-compat-data/pull/27762", "title": "Remove note about Safari time picker for `datetime-local`", "date_modified": "2025-09-05T15:34:55.000Z", "date_published": "2025-09-05T09:18:44.000Z", "author": { "name": "mkurz", "url": "https://github.com/mkurz" } }, { "content_html": "\"\"/

This is a bit of a test PR to see if we could add spec_urls everywhere (especially for behavioral sub features).
\nSome things came up where we should probably agree on spec_url consistency for a few common sub features:

\n\n

Also, I think when a sub aspect of e.g. a method is described then it is okay to link to the same spec section as the method. So, basically the sub feature gets the same spec_url as the parent feature.

\n

I marked standard_track false for a few things: CSSPrimitiveValue, CSSValue, CSSValueList, DOMError, FeaturePolicy. Doesn't look like these will be going anywhere.

\n

Fixes #27456.

", "url": "https://github.com/mdn/browser-compat-data/pull/27671", "title": "Add more spec_urls; set some standard_tracks to false (APIs A-E)", "date_modified": "2025-09-29T11:30:38.000Z", "date_published": "2025-08-26T13:10:28.000Z", "author": { "name": "Elchi3", "url": "https://github.com/Elchi3" } } ] }