Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

browser-specs

Package Overview
Dependencies
Maintainers
4
Versions
224
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

browser-specs - npm Package Compare versions

Comparing version 4.4.0 to 4.5.0

2

package.json
{
"name": "browser-specs",
"version": "4.4.0",
"version": "4.5.0",
"description": "Curated list of technical Web specifications that are directly implemented or that will be implemented by Web browsers.",

@@ -5,0 +5,0 @@ "repository": {

@@ -677,7 +677,10 @@ # Web browser specifications

If you believe that a spec should be added, modified, or removed from the list,
or if you would like to otherwise contribute to this project, please check
[contributing instructions](CONTRIBUTING.md).
If you believe that a spec should be added to the list, check the [selection
criteria](#spec-selection-criteria) below and use the ["New spec" issue
template](https://github.com/w3c/browser-specs/issues/new/choose).
For other types of changes, please check [contributing
instructions](CONTRIBUTING.md).
## Spec selection criteria

@@ -698,3 +701,3 @@

pre-standardization group. Today, this means a W3C Working Group or Community
Group, the WHATWG, the IETF, the TC39 group or the Khronos Group.
Group, the WHATWG, the IETF, the TC39 group, the Khronos Group, the Alliance for Open Media (AOM), or ISO.
4. The spec sits at the application layer or is "close to it". For instance,

@@ -701,0 +704,0 @@ most IETF specs are likely out of scope, but some that are exposed to Web developers are in scope.

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc