vscode-extension
vscode-extension copied to clipboard
Bump @xmldom/xmldom from 0.7.5 to 0.7.6
Bumps @xmldom/xmldom from 0.7.5 to 0.7.6.
Release notes
Sourced from @xmldom/xmldom's releases.
0.7.6
Fixed
- Avoid iterating over prototype properties
[#441](https://github.com/xmldom/xmldom/issues/441)/[#437](https://github.com/xmldom/xmldom/issues/437)/[#436](https://github.com/xmldom/xmldom/issues/436)Thank you,
@jftanner,@Supraja9726for your contributions
Changelog
Sourced from @xmldom/xmldom's changelog.
0.7.6
Fixed
- Avoid iterating over prototype properties
[#441](https://github.com/xmldom/xmldom/issues/441)/[#437](https://github.com/xmldom/xmldom/issues/437)/[#436](https://github.com/xmldom/xmldom/issues/436)Thank you,
@jftanner,@Supraja9726for your contributions0.8.3
Fixed
- Avoid iterating over prototype properties
[#437](https://github.com/xmldom/xmldom/issues/437)/[#436](https://github.com/xmldom/xmldom/issues/436)Thank you,
@Supraja9726for your contributions0.9.0-beta.2
Fixed
- Avoid iterating over prototype properties
[#437](https://github.com/xmldom/xmldom/issues/437)/[#436](https://github.com/xmldom/xmldom/issues/436)Thank you,
@Supraja9726for your contributions0.8.3
Fixed
- Avoid iterating over prototype properties
[#437](https://github.com/xmldom/xmldom/issues/437)/[#436](https://github.com/xmldom/xmldom/issues/436)Thank you,
@Supraja9726for your contributions0.9.0-beta.1
Fixed
Only use HTML rules if mimeType matches
[#338](https://github.com/xmldom/xmldom/issues/338), fixes[#203](https://github.com/xmldom/xmldom/issues/203)In the living specs for parsing XML and HTML, that this library is trying to implement, there is a distinction between the different types of documents being parsed: There are quite some rules that are different for parsing, constructing and serializing XML vs HTML documents.
So far xmldom was always "detecting" whether "the HTML rules should be applied" by looking at the current namespace. So from the first time an the HTML default namespace (
http://www.w3.org/1999/xhtml) was found, every node was treated as being part of an HTML document. This misconception is the root cause for quite some reported bugs.BREAKING CHANGE: HTML rules are no longer applied just because of the namespace, but require the
mimeTypeargument passed toDOMParser.parseFromString(source, mimeType)to match'text/html'. Doing so implies all rules for handling casing for tag and attribute names when parsing, creation of nodes and searching nodes.BREAKING CHANGE: Correct the return type of
DOMParser.parseFromStringtoDocument | undefined. In case of parsing errors it was always possible that "the returnedDocument" has not been created. In case you are using Typescript you now need to handle those cases.BREAKING CHANGE: The instance property
DOMParser.optionsis no longer available, instead use the individualreadonlyproperty per option (assign,domHandler,errorHandler,normalizeLineEndings,locator,xmlns). Those also provides the default value if the option was not passed. The 'locator' option is now just a boolean (default remainstrue).BREAKING CHANGE: The following methods no longer allow a (non spec compliant) boolean argument to toggle "HTML rules":
XMLSerializer.serializeToStringNode.toString
... (truncated)
Commits
3ca016d0.7.6b28e631docs: Prepare CHANGELOG for 0.7.61f20aeefix: Backport PR-437 to 0.7.x branch- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.