github mdn/browser-compat-data v4.0.0

latest releases: v5.3.8, v5.3.7, v5.3.6...
2 years ago

Version 4.0.0 makes some potentially-breaking changes to improve the flexibility and quality of the data. Higlights include:

  • The schema now supports a "preview" version value for in-development browser releases, such as Safari Technology Preview, Chrome Canary, and Firefox Nightly.
  • Deno, the JavaScript and TypeScript runtime, has been added as a new engine.
  • All XPath (xpath) and XSLT (xslt) features have been removed because the data was incomplete and unmaintained.
  • The schema for browser release data now supports the optional accepts_flags boolean hint.

Known issues

  • In v3.3.9, the structure of features for css.properties.place-content, place-items, and place-self changed (#11214). This is an incomplete fix to the problem of undocumented namespaces appearing in places where you might otherwise expect compatability data. The restructuring of the data is a work in progress and may change again in a future release. See #6175 for more information.

Notable changes

  • Deno, the JavaScript and TypeScript runtime, has been added as a new engine. Deno data is included for JavaScript and some Web APIs, much like Node.js data. (#10753)

  • The XPath (xpath) and XSLT (xslt) features have been removed. These features poorly covered their subjects and were unmaintained. Rather than purport to have such data, we removed it.

    We're not ruling out the return of XPath and XSLT data in the future. But for now, in the absence of an intentional effort to create and maintain that data, we thought it best to remove the faulty data. (#9830)

  • The schema now supports a special version value "preview" for in-development versions of browsers, such as Safari Technology Preview, Chrome Canary, and Firefox Nightly. Additionally, browser data now supports a preview_name property for supplying a corresponding name for the preview browser.

    These additions to the schema should help represent features gated to development versions, which were previously misrepresented with notes, false values, or inaccurate version numbers. (#10334)

  • The schema for browser release data now supports the optional accepts_flags boolean hint, which indicates whether a browser (or individual release) should contain flags data. Presently, this is a hint for data contributors or tools. The value of accepts_flags doesn't (yet) make any guarantees about the contents of feature data. (#11286)

  • Descendant features of api.HTMLCanvasElement.getContext and api.HTMLCanvasElement.toBlob have been reorganized to follow the guideline for parameter object features. See the PR for a detailed list of features affected. (#11234)

  • The following features were lower-cased for consistency with other feature names: (#11961)

    • api.CanvasRenderingContext2D.drawImage.Smoothing_downscaling (now smoothing_downscaling)
    • api.OfflineAudioContext.OfflineAudioContext.Parameters_accepted_in_an_object (now parameters_accepted_in_an_object)
  • The following non-existent, long-removed, or otherwise irrelevant features have been removed:

    • api.AnimationEvent.initAnimationEvent (#12059)
    • api.TouchList.identifiedTouch (#11760)

Statistics

  • 22 contributors have changed 406 files with 11,006 additions and 6,128 deletions in 84 commits (v3.3.14...v4.0.0)
  • 13,281 total features
  • 804 total contributors
  • 3,491 total stargazers

Don't miss a new browser-compat-data release

NewReleases is sending notifications on new releases.