Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Some updates based on #1008 #1082

Merged
merged 1 commit into from
Oct 11, 2023
Merged

Some updates based on #1008 #1082

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions specs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,6 +153,14 @@
"https://immersive-web.github.io/anchors/",
"https://immersive-web.github.io/model-element/",
"https://immersive-web.github.io/raw-camera-access/",
{
"url": "https://immersive-web.github.io/real-world-geometry/plane-detection.html",
Copy link
Member

Choose a reason for hiding this comment

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

The IDL of that spec is incomplete (missing [Exposed] on the interface), which IIUC will block the IDL package release down the line. I'm curious if there is a better way to deal with this than just going through the cascade of releases.

Copy link
Member Author

Choose a reason for hiding this comment

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

I do not have a fully satisfactory solution to propose today, either:

  1. we put the spec in the monitor list for now since we know that the IDL is invalid; or
  2. we create a patch; or
  3. we wait until the IDL gets fixed

I'm surprised that we did not seem to have any open issue on the topic, even though we've been floating the idea to improve the curation process in that regard for some time. I created w3c/webref#1055 to track this.

Another option could be to automate checks a bit more when we add a spec to browser-specs, e.g., by running Reffy and tests on the spec and prevent addition of the spec while checks fail. That seems nice in theory but more complex in practice. Also, that wouldn't solve the problem for specs that start to fail after some time.

"shortname": "webxr-plane-detection"
},
{
"url": "https://immersive-web.github.io/real-world-geometry/webxrmeshing-1.html",
"shortname": "webxr-meshing"
},
"https://immersive-web.github.io/real-world-meshing/",
"https://infra.spec.whatwg.org/",
"https://mimesniff.spec.whatwg.org/",
Expand Down Expand Up @@ -455,6 +463,10 @@
"forkOf": "wasm-core-1"
},
"https://webbluetoothcg.github.io/web-bluetooth/",
{
"url": "https://webbluetoothcg.github.io/web-bluetooth/scanning.html",
"shortname": "web-bluetooth-scanning"
},
"https://webidl.spec.whatwg.org/",
"https://websockets.spec.whatwg.org/",
"https://wicg.github.io/attribution-reporting-api/",
Expand Down Expand Up @@ -566,6 +578,10 @@
"https://wicg.github.io/web-app-launch/",
"https://wicg.github.io/web-otp/",
"https://wicg.github.io/web-preferences-api/",
{
"url": "https://wicg.github.io/WebApiDevice/managed_config/",
"shortname": "managed-configuration"
},
"https://wicg.github.io/webcrypto-secure-curves/",
"https://wicg.github.io/webhid/",
"https://wicg.github.io/webpackage/loading.html",
Expand Down Expand Up @@ -1026,6 +1042,12 @@
"https://www.w3.org/TR/magnetometer/",
"https://www.w3.org/TR/manifest-app-info/",
"https://www.w3.org/TR/mathml-core/",
{
"url": "https://www.w3.org/TR/mathml4/",
"categories": [
"-browser"
]
},
"https://www.w3.org/TR/media-capabilities/",
{
"url": "https://www.w3.org/TR/media-source-2/",
Expand Down
27 changes: 24 additions & 3 deletions src/data/ignore.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,9 +47,6 @@
}
},
"repos": {
"w3c/mathml": {
"comment": "not targeted at browsers"
},
"w3c/adpt": {
"comment": "not targeted at browsers"
},
Expand Down Expand Up @@ -411,6 +408,30 @@
},
"https://w3c.github.io/resource-hints/": {
"comment": "Integrated in HTML, ED redirects to HTML"
},
"https://w3c.github.io/webpayments-http-messages/": {
"comment": "no longer worked on"
},
"https://draft.ortc.org/": {
"comment": "No expectation that the API will be implemented in browsers"
},
"https://webmachinelearning.github.io/model-loader/": {
"comment": "no longer worked on"
},
"https://w3c.github.io/webpayments-crypto/": {
"comment": "no longer worked on"
},
"https://w3c.github.io/webpayments-methods-tokenization/": {
"comment": "no longer worked on"
},
"https://w3c.github.io/merchant-validation/": {
"comment": "no longer worked on"
},
"https://tabatkins.github.io/css-toggle/": {
"comment": "Proposal in a personal repository, no adoption from community"
},
"https://tabatkins.github.io/specs/css-stacking-context-1/": {
"comment": "Proposal in a personal repository, no adoption from community"
}
}
}
4 changes: 4 additions & 0 deletions src/data/monitor.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -339,6 +339,10 @@
"WICG/coop-restrict-properties": {
"lastreviewed": "2023-10-09",
"comment": "no published content yet"
},
"patcg-individual-drafts/private-aggregation-api": {
"lastreviewed": "2023-10-10",
"comment": "proposal has not been adopted by the Private Advertising Technology Community Group"
}
},
"specs": {
Expand Down