Bump jsdom from 16.2.2 to 16.7.0

[dependabot]

Bumps jsdom from 16.2.2 to 16.7.0.

Release notes

Sourced from jsdom's releases.

Version 16.7.0

• Added AbortSignal.abort(). (ninevra)
• Added dummy x and y properties to the return value of getBoundingClientRect(). (eiko)
• Implemented wrapping for textareaEl.value if the wrap="" attribute is specified. (ninevra)
• Changed newline normalization in <textarea>s according to recent HTML Standard updates. (ninevra)
• Fixed some bad cascade computation in getComputedStyle(). (romain-trotard)

Version 16.6.0

• Added parentNode.replaceChildren(). (@​ninevra)
• Fixed jsdom's handling of when code running inside the jsdom throws null or undefined as an exception. (@​mbest)
• Removed the dependency on the deprecated request package, in the process fixing several issues with the XMLHttpRequest implementation around header processing. Thanks go to @​tobyhinloopen, @​andrewaylett, and especially @​vegardbb, for completing this months-long effort!

Version 16.5.3

• Fixed infinite recursion when using MutationObservers to observe elements inside a MutationObserver callback.

Version 16.5.2

• Fixed Access-Control-Allow-Headers: * to work with XMLHttpRequest. (silviot)
• Fixed xhr.response to strip any leading BOM when xhr.responseType is "json".
• Fixed new Text() and new Comment() constructors to properly set the resulting node's ownerDocument.
• Fixed customElements.whenDefined() to resolve its returned promise with the custom element constructor, per recent spec updates. (ExE-Boss)
• Fixed parsing to ensure that <svg>\<template></template></svg> does not throw an exception, but instead correctly produces a SVG-namespace \<template> element.
• Fixed domParser.parseFromString() to treat <noscript> elements appropriately.
• Fixed form control validity checking when the control was outside the <form> element and instead associated using the form="" attribute.
• Fixed legendEl.form to return the correct result based on its parent <fieldset>.
• Fixed optionEl.text to exclude <script> descendants.
• Fixed radio buttons and checkboxes to not fire input and change events when disconnected.
• Fixed inputEl.indeterminate to reset to its previous value when canceling a click event on a checkbox or radio button.
• Fixed the behavior of event handler attributes (e.g. onclick="...code...") when there were global variables named element or formOwner. (ExE-Boss)
• On Node.js v14.6.0+ where WeakRefs are available, fixed NodeIterator to no longer stop working when more than ten NodeIterator instances are created, and to use less memory due to inactive NodeIterators sticking around. (ExE-Boss)

Version 16.5.1

• Fixed a regression that broke customElements.get() in v16.5.0. (fdesforges)
• Fixed window.event to have a setter which overwrites the window.event property with the given value, per the specification. This fixes an issue where after upgrading to jsdom v16.5.0 you would no longer be able to set a global variable named event in the jsdom context.

Version 16.5.0

• Added window.queueMicrotask().
• Added window.event.
• Added inputEvent.inputType. (diegohaz)
• Removed ondragexit from Window and friends, per a spec update.
• Fixed the URL of about:blank iframes. Previously it was getting set to the parent's URL. (SimonMueller)
• Fixed the loading of subresources from the filesystem when they had non-ASCII filenames.
• Fixed the hidden="" attribute to cause display: none per the user-agent stylesheet. (ph-fritsche)
• Fixed the new File() constructor to no longer convert / to :, per a pending spec update.
• Fixed mutation observer callbacks to be called with the MutationObserver instance as their this value.
• Fixed <input type=checkbox> and <input type=radio> to be mutable even when disabled, per a spec update.
• Fixed XMLHttpRequest to not fire a redundant final progress event if a progress event was previously fired with the same loaded value. This would usually occur with small files.
• Fixed XMLHttpRequest to expose the Content-Length header on cross-origin responses.
• Fixed xhr.response to return null for failures that occur during the middle of the download.
• Fixed edge cases around passing callback functions or event handlers. (ExE-Boss)
• Fixed edge cases around the properties of proxy-like objects such as localStorage or dataset. (ExE-Boss)

... (truncated)

Changelog

Sourced from jsdom's changelog.

16.7.0

• Added AbortSignal.abort(). (ninevra)
• Added dummy x and y properties to the return value of getBoundingClientRect(). (eiko)
• Implemented wrapping for textareaEl.value if the wrap="" attribute is specified. (ninevra)
• Changed newline normalization in <textarea>s according to recent HTML Standard updates. (ninevra)
• Fixed some bad cascade computation in getComputedStyle(). (romain-trotard)

16.6.0

• Added parentNode.replaceChildren(). (ninevra)
• Fixed jsdom's handling of when code running inside the jsdom throws null or undefined as an exception. (mbest)
• Removed the dependency on the deprecated request package, in the process fixing several issues with the XMLHttpRequest implementation around header processing. Special thanks to vegardbb for completing this months-long effort!

16.5.3

• Fixed infinite recursion when using MutationObservers to observe elements inside a MutationObserver callback.

16.5.2

• Fixed Access-Control-Allow-Headers: * to work with XMLHttpRequest. (silviot)
• Fixed xhr.response to strip any leading BOM when xhr.responseType is "json".
• Fixed new Text() and new Comment() constructors to properly set the resulting node's ownerDocument.
• Fixed customElements.whenDefined() to resolve its returned promise with the custom element constructor, per recent spec updates. (ExE-Boss)
• Fixed parsing to ensure that <svg>\<template></template></svg> does not throw an exception, but instead correctly produces a SVG-namespace \<template> element.
• Fixed domParser.parseFromString() to treat <noscript> elements appropriately.
• Fixed form control validity checking when the control was outside the <form> element and instead associated using the form="" attribute.
• Fixed legendEl.form to return the correct result based on its parent <fieldset>.
• Fixed optionEl.text to exclude <script> descendants.
• Fixed radio buttons and checkboxes to not fire input and change events when disconnected.
• Fixed inputEl.indeterminate to reset to its previous value when canceling a click event on a checkbox or radio button.
• Fixed the behavior of event handler attributes (e.g. onclick="...code...") when there were global variables named element or formOwner. (ExE-Boss)
• On Node.js v14.6.0+ where WeakRefs are available, fixed NodeIterator to no longer stop working when more than ten NodeIterator instances are created, and to use less memory due to inactive NodeIterators sticking around. (ExE-Boss)

16.5.1

• Fixed a regression that broke customElements.get() in v16.5.0. (fdesforges)
• Fixed window.event to have a setter which overwrites the window.event property with the given value, per the specification. This fixes an issue where after upgrading to jsdom v16.5.0 you would no longer be able to set a global variable named event in the jsdom context.

16.5.0

• Added window.queueMicrotask().
• Added window.event.
• Added inputEvent.inputType. (diegohaz)
• Removed ondragexit from Window and friends, per a spec update.
• Fixed the URL of about:blank iframes. Previously it was getting set to the parent's URL. (SimonMueller)
• Fixed the loading of subresources from the filesystem when they had non-ASCII filenames.
• Fixed the hidden="" attribute to cause display: none per the user-agent stylesheet. (ph-fritsche)
• Fixed the new File() constructor to no longer convert / to :, per a pending spec update.
• Fixed mutation observer callbacks to be called with the MutationObserver instance as their this value.

... (truncated)

Commits

• 1aa3cbc Version 16.7.0
• df1f551 Don't run WebSocketStream tests
• eb105b2 Fix browser tests by enabling SharedArrayBuffer
• 0dedfc0 Fix some bad cascade computation in getComputedStyle()
• 8021a56 Fix "configuation" typo (#3213)
• a7febe3 Fix typo in level2/html.js (#3222)
• c9896c0 Return x, y properties from Element.getBoundingClientRect (#3187)
• 346ea98 Update web-platform tests (#3203)
• 364c77d Bump to ws 7.4.6
• 93ba6a0 We are now on Matrix (#3207)
• Additional commits viewable 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will 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 version will 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 dependency will 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 labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will 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.

[pull-request-quantifier-deprecated]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : No Changes
Size       : +0 -0
Percentile : 0%

Total files changed: 1

Change summary by file extension:
.json : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.