Conversation
sideshowbarker
approved these changes
Apr 12, 2021
5 tasks
Contributor
|
Speaking of breaking changes, I remember there were a few incorrectly named features. Since feature renaming might break dependents, we might want to rename them all at once.
|
Contributor
Author
|
@bershanskiy thanks for flagging that. I do record renames like that in the release notes (and add the needs-release-note label to applicable PRs). That said, we're not using all feature name-changes trigger a semver major release (we tried to document this at https://github.com/mdn/browser-compat-data#semantic-versioning-policy). |
11 tasks
Contributor
|
This PR should probably also close #2027 if/when it is merged, which is an issue to track the progress of migrating the remaining XSLT compat data. |
sideshowbarker
approved these changes
Jun 4, 2021
d88c330 to
b243bfb
Compare
sideshowbarker
approved these changes
Aug 17, 2021
Member
|
(You should remove the 🛤️ and 🚜 labels from BCD) |
ddbeck
added a commit
to ddbeck/browser-compat-data
that referenced
this pull request
Aug 17, 2021
ddbeck
added a commit
that referenced
this pull request
Aug 19, 2021
* Bump version to v4.0.0 * Add release note for #11234 * Bump known issues * Add release note for #11760 * Add release note for #11286 * Add release note for #9830 * Add release note for #10334 * Add v4.0.0 highlights to release notes * Add release note for #10753 * Revise description of `accepts_flags` hint * Add release note for #11961 * Add release note for #12059 * Add stats
This file contains hidden or 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
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.
cc: @Elchi3, @sideshowbarker
This PR is in draft status, until there's another set of breaking changes we can roll this up with.
This PR drops XPath and XSLT data, as well as associated schema, linting, docs, etc. This data is very incomplete. We're not foreclosing on this data returning at some point, but if it comes back, it needs to be in the context of an intentional effort.
Potentially affected MDN URLs
xslt.elements.stylesheetxslt.elements.stylesheet.exclude-result-prefixesxslt.elements.stylesheet.extension-element-prefixesxslt.elements.stylesheet.idxslt.elements.stylesheet.versionxslt.exslt.exsl.node-setxslt.exslt.exsl.object-typexslt.exslt.math.highestxslt.exslt.math.lowestxslt.exslt.math.maxxslt.exslt.math.minxslt.exslt.regexp.matchxslt.exslt.regexp.replacexslt.exslt.regexp.testxslt.exslt.set.differencexslt.exslt.set.distinctxslt.exslt.set.has-same-nodexslt.exslt.set.intersectionxslt.exslt.set.leadingxslt.exslt.set.trailingxslt.exslt.str.concatxslt.exslt.str.splitxslt.exslt.str.tokenizexpath.axes.self