Add/Fix META.yml files to ease specs to WPT mapping #26970
Merged
Conversation
This file contains 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
This commit fixes `spec` entries in `META.yml` files that were pointing to the wrong URL (either because the URL is a broken link, redirects to a newer URL, or targets the GitHub repository instead of the spec itself), so that it becomes easier to map specifications to WPT folders based on the URL of their Editor/Living Draft. This commit also adds several `META.yml` files to folders that cannot easily be mapped to a spec because their name does not match the spec's shortname.
wpt-pr-bot
added
BackgroundSync
client-hints
compression
contacts
content-security-policy
css-inline
css-overscroll-behavior
css-parser-api
event-timing
fetch
geolocation-sensor
idle-detection
import-maps
input-device-capabilities
keyboard-lock
lifecycle
media-capabilities
mediasession
picture-in-picture
scroll-animations
scroll-to-text-fragment
speech-api
storage-access-api
timing-entrytypes-registry
video-rvfc
wasm
webcodecs
webrtc-identity
webxr
labels
wpt-pr-bot
requested review from
andrenatal,
andypaicu,
annevk,
anssiko,
beaufortfrancois,
beverloo,
birtles,
Brandr0id,
dauwhe,
domenic,
domfarolino,
fantasai,
fmeawad,
foolip and
garykac
foolip
approved these changes
Dec 21, 2020
|
Awesome, thanks @tidoust! Since touching many directories will subscribe lots of people, I'll merge this. Please feel free to open another PR for the remaining cases, that would be much appreciated! |
This was referenced Dec 22, 2020
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.
I am trying to map specs listed in w3c/browser-specs to their test suites in WPT. Thanks to
META.ymlfiles, I can map about 200 specs in that list directly to a WPT folder based on the spec's URL. I can also associate 30 other specs with WPT folders that do not link to a spec explicitly based on the spec's shortname.There remain 32 cases for which the spec and folder cannot be directly associated because:
META.ymlfile is not the right one, either because it targets an outdated version of the spec (e.g. because the spec has migrated from WICG to a working group), because it targets the GitHub repository instead of the spec itself, or simply because it is invalid.META.ymlfile or there is noMETA.ymlfile, and the folder's name does not match the spec's shortname.This pull request fixes these cases.
I would also be happy to add
META.ymlfiles for the 30 folders that do not expose a URL and that I can only map based on their name, so that the mapping uses a consistent mechanism throughout. Should I complete the PR? Here is the list:List of folders that can only be mapped to a spec based on their name
badging=> Badging APIcontent-index=> Content Indexcss/css-color-adjust=> CSS Color Adjustment Module Level 1css/css-scroll-anchoring=> CSS Scroll Anchoring Module Level 1css/css-size-adjust=> CSS Mobile Text Size Adjustment Module Level 1custom-state-pseudo-class=> Custom State Pseudo Classdeprecation-reporting=> Deprecation Reportingintervention-reporting=> Intervention Reportingis-input-pending=> isInputPendingjs-self-profiling=> JS Self-Profiling APInetwork-error-logging=> Network Error Loggingorigin-policy=> Origin Policypage-lifecycle=> Page Lifecyclepermissions-request=> Requesting Permissionspermissions-revoke=> Relinquishing Permissionssavedata=> Save Data APIserial=> Web Serial APItrusted-types=> Trusted Typesua-client-hints=> User-Agent Client Hintsweb-otp=> Web OTP APIwebhid=> WebHID APIwebrtc-insertable-streams=> WebRTC Insertable Media using Streamswebrtc-priority=> WebRTC Priority Control APIwebrtc-svc=> Scalable Video Coding (SVC) Extension for WebRTCwebtransport=> WebTransportwebxr/anchors=> WebXR Anchors Modulewebxr/ar-module=> WebXR Augmented Reality Module - Level 1webxr/gamepads-module=> WebXR Gamepads Module - Level 1webxr/hand-input=> WebXR Hand Input Module - Level 1webxr/hit-test=> WebXR Hit Test ModuleI note that there exist both a
lifecycleand apage-lifecyclefolder for the Page Lifecycle specification. Is that intended?Linked to w3c/browser-specs#201