-
Notifications
You must be signed in to change notification settings - Fork 2k
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.
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
Remove XPath and XSLT data #9830
Conversation
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.
|
@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). |
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. |
d88c330
to
b243bfb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No more 🛤️ and 🚜 !!! 😄
(You should remove the 🛤️ and 🚜 labels from BCD) |
* 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
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.stylesheet
xslt.elements.stylesheet.exclude-result-prefixes
xslt.elements.stylesheet.extension-element-prefixes
xslt.elements.stylesheet.id
xslt.elements.stylesheet.version
xslt.exslt.exsl.node-set
xslt.exslt.exsl.object-type
xslt.exslt.math.highest
xslt.exslt.math.lowest
xslt.exslt.math.max
xslt.exslt.math.min
xslt.exslt.regexp.match
xslt.exslt.regexp.replace
xslt.exslt.regexp.test
xslt.exslt.set.difference
xslt.exslt.set.distinct
xslt.exslt.set.has-same-node
xslt.exslt.set.intersection
xslt.exslt.set.leading
xslt.exslt.set.trailing
xslt.exslt.str.concat
xslt.exslt.str.split
xslt.exslt.str.tokenize
xpath.axes.self