📦 Release [email protected] #1628
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
release-web-specs-20250106182718361
branch
from
0752b19 to
8cb84e6
Compare
github-actions
bot
force-pushed
the
release-web-specs-20250106182718361
branch
from
8cb84e6 to
bdf797f
Compare
github-actions
bot
changed the title
github-actions
bot
force-pushed
the
release-web-specs-20250106182718361
branch
from
bdf797f to
08494af
Compare
|
With the move away from Specref for WICG specs, three specs that say they are "unofficial drafts" moved to "pending". That's good, they should have been added as "pending" to start with. Now, two of them are already in WPT, so we probably want to keep a "good" standing for them:
|
tidoust
added a commit
that referenced
this pull request
Jan 13, 2025
See discussion in: #1628 (comment) Specs used to come with a "good" standing in browser-specs because data came from Specref. The specs themselves continue to say they are unofficial drafts, and so build code now considers that these specs should have a "pending" standing. That standing seems correct, but WPT already has actual tests for the CSS Parser API (on top of IDL tests), and already integrated the preferCurrentTab IDL as well (just a partial dictionary definition in practice). This update forces the standing to "good" for continuity.
tidoust
added a commit
that referenced
this pull request
Jan 13, 2025
See discussion in: #1628 (comment) Specs used to come with a "good" standing in browser-specs because data came from Specref. The specs themselves continue to say they are unofficial drafts, and so build code now considers that these specs should have a "pending" standing. That standing seems correct, but WPT already has actual tests for the CSS Parser API (on top of IDL tests), and already integrated the preferCurrentTab IDL as well (just a partial dictionary definition in practice). This update forces the standing to "good" for continuity.
github-actions
bot
force-pushed
the
release-web-specs-20250106182718361
branch
from
08494af to
65e5ac2
Compare
BCD (and MDN) used https://w3c.github.io/web-share-target/#share_target-member as the valid spec url for https://developer.mozilla.org/en-US/docs/Web/Manifest/share_target#specifications Given it is now pending, I will remove it with our web-specs update in mdn/browser-compat-data#25650. |
tidoust
added a commit
that referenced
this pull request
Jan 14, 2025
The spec is documented on MDN already, so the switch to "pending" is not fantastic for BCD and web-features. See context in: #1645 #1628 (comment)
|
I thought the transition to "pending" would not have any practical consequence on that one. I had not realized that the feature was already documented on MDN. Now planning to rollback to a "good" standing for the spec in #1646. |
tidoust
added a commit
that referenced
this pull request
Jan 14, 2025
The spec is documented on MDN already, so the switch to "pending" is not fantastic for BCD and web-features. See context in: #1645 #1628 (comment)
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.
⚠ NEVER add commits to this pull request.
🤖 This pull request was automatically created to facilitate human review of
web-specschanges based on list of specs at 1677049.🧐 Please review the diff below and version numbers. If all looks good, merge this pull request to release the changes to npm.
📦 Latest released
web-specspackage was v3.32.0. Merging this pull request will release v3.33.0. Make sure that the bump is the right one for the changes.✍ If any change needs to be made before release, do not add a commit to this pull request. Changes should rather be handled in a separate pull request and pushed to the main branch. You may leave this pull request open in the meantime, or close it. The pre-release job will automatically update this pull request or create a new one once the updates have made their way to the main branch.
🛈 The actual change introduced by this pull request is a version bump in
packages/web-specs/package.json. You do not need to review that change. The bumped version is not the version that will be released when this pull request is merged, but rather the version that will be released next time.