Closed greenkeeper[bot] closed 7 years ago
Update to this version instead ๐
The new version differs by 15 commits0.
d078830
Version 10.1.0
e3e4629
Enable FormData being iterable
8d3f747
Implement HTMLSelectElement's selectedOptions
e79e9a1
Fix xhr.abort() during XHR readystatechange
270f288
Pre-allocate XMLHttpRequest buffer
2552a85
Disable flaky XHR tests
8c1709b
Clear the "generated" directory each run
ca8dfef
Ensure { runScripts: "outside-only" } also passes down to iframes
3d0f28d
Properly inherit "document features" configuration into iframes
1f488ec
Remove stray toString directly on Window
9d0c03e
Use Symbol.toStringTag to make Object.prototype.toString work
4591c3c
Fix TODO links to the paper about jsdom in a web worker
ac49743
Implement value sanitization algorithms for several input types
b2bfc3d
Add an issue template
aea99cd
Document fix to img load events in the v10 changelog
false
See the full diff
Update to this version instead ๐
The new version differs by 40 commits.
0f4128d
Version 11.0.0
be65539
Fix event handler property generation to properly rely on runScripts
38c430f
Factor out runScripts option tests
ecf7449
Do not submit disconnected form elements
5f3cbd6
Properly implement event handler properties/attributes
3eb19e7
Remove a few more now-redundant toString()s
b1b7f23
Refactor XHR's send() implementation
7d950c4
Delete keygen from default stylesheet
5151546
Remove other unsupported CSS features from the default stylesheet
dfc9430
Delete webkit prefixes and other internal selectors in default CSS
56fbd0d
Support ArrayBufferViews in xhr.send()
ce13678
Disable yet another flaky-on-CI XHR test
dabf1a4
Remove createCDATASection from benchmarks
2d257ef
Update benchmark runner to support the new API
1833f78
Use Set instead of Array for HTMLCollection keys
There are 40 commits in total.
See the full diff
Will be closed with #497
Version 10.0.0 of jsdom just got published.
The version 10.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of jsdom. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 9 commits0.
50ebb59
Version 10.0.0
c854f7e
Small updates to the readme and to JS feature usage
380e2fe
Forward approved preflight headers to request during XHR
3a1c2e0
Fix htmlElement.dir and implement document.dir
3aca01a
Update / API to match current specs
fa74ef9
Fix origin-checking logic in postMessage
4513ba1
Improve xhr.open not enough args error message
461c638
Handle setting innerHTML to the empty string
58a7028
Overhaul the public jsdom API
false
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: