Version 10.1.0

AUTHORS.txt

@@ -225,5 +225,6 @@ Wei Dai <x@wei23.net>
 William Cunningham <w.a.cunningham.ii@gmail.com>
 Xavi <xavi.rmz@gmail.com>
 Yonathan <yonathan@gmail.com>
+Yun Cui <ycui@microstrategy.com>
 Zach Smith <zach@amicushq.com>
 Zirro <code@zirro.se>

Changelog.md

@@ -1,3 +1,14 @@
+## 10.1.0
+
+* Added the value sanitization algorithm for password, search, tel, text, color, email, and url input types. (Zirro)
+* Added `Symbol.toStringTag` to all web platform classes, so that now `Object.prototype.toString.call()` works as expected on jsdom objects.
+* Added the `select.selectedOptions` property.
+* Removed the `toString()` methods on various prototypes that returned `"[object ClassName]"` in an attempt to fake the `Symbol.toStringTag` behavior.
+* Changed `XMLHttpRequest` to pre-allocate a 1 MiB buffer, which it grows exponentially as needed, in order to avoid frequent buffer allocation and concatenation. (skygon)
+* Fixed a variety of properties that were meant to always return the same object, to actually do so. (Zirro)
+* Fixed inheritance of the `runScripts` and `resources` options into iframes.
+* Fixed an uncaught exception that occurred if you called `xhr.abort()` during a `"readystatechange"` event.
+
 ## 10.0.0
 
 This release includes a complete overhaul of jsdom's API for creating and manipulating jsdoms. The new API is meant to be much more intuitive and have better defaults, with complete documentation in the newly-overhauled README. We hope you like it!

README.md

@@ -416,7 +416,7 @@ Nevertheless, we remain interested in one day providing an option to create an "
 
 ### Missing features in the new API
 
-Compared to the old JSDOM API from v9.x and before, the new API is noticably missing fine-grained control of resource loads. Previous versions of jsdom allowed you to set options that were used when making requests (both for the initial request, in the old equivalent of `JSDOM.fromURL()`, and for subresource requests). They also allowed you to control which subresources were requested and applied to the main document, so that you could e.g. download stylesheets but not scripts. Finally, they provided a customizable resource loader that let you intercept any outgoing request and fulfill it with a completely synthetic response.
+Compared to the old jsdom API from v9.x and before, the new API is noticably missing fine-grained control of resource loads. Previous versions of jsdom allowed you to set options that were used when making requests (both for the initial request, in the old equivalent of `JSDOM.fromURL()`, and for subresource requests). They also allowed you to control which subresources were requested and applied to the main document, so that you could e.g. download stylesheets but not scripts. Finally, they provided a customizable resource loader that let you intercept any outgoing request and fulfill it with a completely synthetic response.
 
 None of these features are yet in the new jsdom API, although we are hoping to add them back soon! This requires a decent amount of behind-the-scenes work to implement in a reasonable way, unfortunately.
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "jsdom",
-  "version": "10.0.0",
+  "version": "10.1.0",
   "description": "A JavaScript implementation of many web standards",
   "keywords": [
     "dom",