jsdom

• Fix: HTMLInputElement.prototype.checked and defaultChecked now behave per the spec. (@Joris-van-der-Wel)
• Fix: HTMLOptionElement.prototype.selected now behaves per the spec. (@Joris-van-der-Wel)
• Fix: HTMLInputElement.prototype.value now behaves per the spec. (@Joris-van-der-Wel)
• Fix: HTMLTextAreaElement.prototype.value and defaultValue now behave per the spec. (@Joris-van-der-Wel)
• Add: HTMLTextAreaElement.prototype.defaultValue now has a setter, and HTMLTextAreaElement.prototype.textLength now exists. (@Joris-van-der-Wel)
• Fix: resetting a <form> now behaves per spec for all different types of form elements. (@Joris-van-der-Wel)
• Fix: radio buttons reset other radio buttons correctly now per the spec. (@Joris-van-der-Wel)
• Fix: document.cloneNode now works. (@AVGP)
• Fix: hasAttribute is now case-insensitive, as it should be. (@AVGP)
• Fix: div.toString() now returns [object HTMLDivElement]. (@AVGP)

• Fix: check if module.parent exists before using it to construct a document's initial URL. Apparently some testing frameworks like Jest do not correctly emulate the module environment; this compensates. (@SegFaultx64)

• Fix: changing attributes on <option> elements will now have the correct consequences. For example changing the id attribute now interacts correctly with document.getElementById. (@Joris-van-der-Wel)

• Add: moved focus and blur methods to HTMLElement.prototype, instead of having them only be present on certain element prototypes. Our focus story is still not very spec-compliant, but this is a step in the right direction. (@vincentsiao)

• Tweak: improve performance of Node.prototype.insertBefore, Node.prototype.removeChild, and several AttributeList methods. (@Joris-van-der-Wel)

• Fix: querySelectorAll correctly coerces its argument to a string; notably this allows you to pass arrays. (@jeffcarp)
• Fix: the data setter on text nodes correctly coerces the new value to a string. (@medikoo)
• Fix: document.toString() now returns [object HTMLDocument]. (@jeffcarp)

• Fix: handling of <template> element parsing and serialization, now that it is supported by parse5. (@inikulin)

• Add: NodeFilter, in particular its constants. (@fhemberger)
• Fix: initial history.length should be 1, not 0. (@rgrove)
• Fix: history.pushState and history.replaceState should not fire the popstate event. (@rgrove)

• Add: document.implementation.createHTMLDocument(). (@fhemberger)
• Fix: localName was sometimes null for elements when it should not be. (@fhemberger)

• Update: no longer requiring separate cssstyle and cssstyle-browserify dependencies; now cssstyle can be used directly. This also un-pins the cssstyle dependency so that future fixes arrive as they appear upstream.

• Fix: temporarily pin cssstyle dependency to at most 0.2.18 until chad3814/CSSStyleDeclaration#20 is fixed.
• Fix: browserifying jsdom should work better now that the required packages are included as dependencies instead of devDependencies. (@Sebmaster)
• Fix: using jsdom.env in a browser environment now correctly defaults options.url to location.href instead of trying to infer a reasonable fil:// URL using techniques that fail in the browser. (@rattrayalex)

• Fix: the return value of EventTarget.prototype.dispatchEvent should be true when the default is not prevented; previously it was the opposite. (@eventualbuddha)

For a consolidated list of changes from 0.11.1 to 1.0.0, see this wiki page.

• Remove: nonstandard EventTarget.getListeners; EventTarget.forwardIterator; EventTarget.backwardIterator; EventTarget.singleIterator.
• Remove: nonstandard document.innerHTML. (@jorendorff)
• Fix: value and defaultValue properties of a HTMLInputElement are now correctly synced to the value="" attribute. (@Sebmaster)

• Remove: support for old, untested HTML and XML parsers, namely davglass/node-htmlparser and isaacs/sax-js. In the future we plan to work toward a standardized parsing interface that other parsers can implement, instead of adding custom code to jsdom for various parsers. This interface still is being decided though, as it needs to support complex things like pausing the parse stream (for document.write) and parsing disconnected fragments (for document.innerHTML). (@Sebmaster)
• Add: new parsingMode configuration, to allow you to manually specify XML or HTML. (@Sebmaster)
• Change: jsdom will no longer use the presence of <?xml or similar to attempt to auto-detect XHTML documents. Instead, it will by default treat them the same as browsers do, with the <?xml declaration just being a bogus comment. If you need your document interpreted as XHTML instead of HTML, use the parsingMode option. (@Sebmaster)
• Tweak: memoize various DOM-querying functions (e.g. getElementsByTagName, querySelector, etc.) to improve performance. (@ccarpita)

• Fix: another parsing issues with void elements and innerHTML, this time related to disconnected nodes. This was a regression between 0.11.1 and 1.0.0-pre.1. (@paton)
• Fix: same-named radio inputs should not be mutually exclusive unless they are in the same form. (@stof)

• Fix: sometimes calling window.close() would cause a segfault. (@paton)

• Fix: attributes and elements now have their prefix, localName, and namespaceURI properties set correctly in all cases. (Excepting application/xhtml+xml mode, which jsdom does not support yet.) (@Sebmaster)

• Fix: parsing and serialization of attributes in the form x:y, e.g. xmlns:xlink or xlink:href. This was a regression between 0.11.1 and 1.0.0-pre.1. (@Sebmaster)

• Fix: void elements no longer parsed correctly when using innerHTML. This was a regression between 0.11.1 and 1.0.0-pre.1. (@Sebmaster)

This is a prerelease of jsdom's first major version. It incorporates several great additions, as well as a general cleanup of the API surface, which make it more backward-incompatible than usual. Starting with the 1.0.0 release, we will be following semantic versioning, so that you can depend on stability within major version ranges. But we still have a few more issues before we can get there, so I don't want to do 1.0.0 quite yet.

This release owes a special thanks to @Sebmaster, for his amazing work taking on some of the hardest problems in jsdom and solving them with gusto.

Major changes

• jsdom now can be browserified into a bundle that works in web workers! This is highly experimental, but also highly exciting! (@lawnsea)
• An overhaul of the initialization lifecycle, to bring more control and address common use cases. (@Sebmaster)
• The excellent parse5 HTML parser is now the default parser, fixing many parsing bugs and giving us full, official-test-suite-passing HTML parsing support. This especially impacts documents that didn't include optional tags like <html>, <head>, or <body> in their source. We also use parse5 for serialization, fixing many bugs there. (@Sebmaster)
• As part of the new parser story, we are not supporting XML for now. It might work if you switch to a different parser (e.g. htmlparser2), but in the end, HTML and XML are very different, and we are not attempting to be an XML DOM. That said, we eventually want to support XML to the same extent browsers do (i.e., support XHTML and SVG, with an appropriate MIME type switch); this is being planned in #820.

Removed jsdom APIs

• jsdom.createWindow: use document.parentWindow after creating a document
• jsdom.html: use jsdom.jsdom
• jsdom.version: use require("jsdom/package.json").version
• jsdom.level: levels are deprecated and will probably be removed in 2.0.0
• jsdom.dom
• jsdom.browserAugmentation
• jsdom.windowAugmentation

Changed jsdom APIs

• jsdom.jsdom no longer takes a level as its second argument.
• jsdom.jQueryify now requires a jQuery URL, since always picking the latest was a bad idea.

Removed non-standard DOM APIs

• document.createWindow: use document.parentWindow
• document.innerHTML and document.outerHTML: use the new jsdom.serializeDocument to include the DOCTYPE, or use document.documentElement.outerHTML to omit it.

Other fixes

• Allow empty strings to be passed to jsdom.env. (@michaelmior)
• Fix for a memory leak in EventTarget.prototype.dispatchEvent. (@Joris-van-der-Wel)
• Make event listeners in the capture phase also fire on the event target. (@Joris-van-der-Wel)
• Correctly reset eventPhase and currentTarget on events, before and after a dispatch. (@Joris-van-der-Wel)
• Fix document.cookie = null to not throw, but instead just do nothing. (@kapouer)

• Add: Node.prototype.parentElement. (@lukasbuenger)
• Fix: attributes that are reflected as properties should be '' when not present, instead of null. (Note that getAttribute still returns null for them). (@thejameskyle)
• Fix: textContent now works for nodes that do not have children, like text nodes for example. (@hayes)
• Fix: jsdom.jQueryify was using the wrong URL for jQuery by default. (@lukasbuenger)

• Add: new default level, living, reflecting our focus on the DOM Living Standard and the HTML Living Standard, which are what browsers actually implement. This should open the door for more features of the modern DOM and HTML specs to be implemented in jsdom. (@robotlovesyou)
• Add: Node.prototype.contains now implemented. (@robotlovesyou)
• Add: navigator.cookieEnabled now implemented; it always returns true. (@Sebmaster)
• Change: DOCTYPEs no longer have their name property uppercased during parsing, and appear in the output of document.innerHTML.
• Fix: Node.prototype.compareDocumentPosition implemented correctly; various document position constants added to the Node constructor. (@robotlovesyou)
• Fix: DocumentType.prototype.parentNode now returns the document node, not null. (@robotlovesyou)
• Fix: various navigator properties are now getters, not data properties. (@Sebmaster)
• Fix: a bug involving invalid script paths and jsdom.jQueryify. (@Sebmaster)

• Add: remaining URL properties to window.location and HTMLAnchorElement.
• Fix: the presence of String.prototype.normalize, which is available by default in Node 0.11.13 onwards, caused reflected attributes to break. (@brock8503)
• Fix: iframes now correctly load about:blank when the src attribute is empty or missing. (@mcmathja)
• Fix: documents containing only whitespace now correctly generate wrapper documents, just like blank documents do. (@nikolas)
• Tweak: lazy-load the request module, to improve overall jsdom loading time. (@tantaman)

• Fix: the list of void elements has been updated to match the latest HTML spec.
• Fix: when serializing void elements, don't include a /: i.e. the result is now <br> instead of <br />.

• Fix: another case was found where jQuery 1.11's show() method would cause errors.
• Add: querySelector and querySelectorAll methods to DocumentFragments. (@Joris-van-der-Wel)

• Fix: various defaults on HTMLAnchorElement and window.location should not be null; they should usually be the empty string.

• Fix: Using jQuery 1.11's show() method would cause an error to be thrown.
• Fix: window.location properties were not updating correctly after using pushState or replaceState. (@toomanydaves)

• Fix: window.location.port should default to "", not null. (@bpeacock)

• Add: a more complete document.cookie implementation, that supports multiple cookies. Note that options like path, max-age, etc. are still ignored. (@dai-shi)

• Add: implement attribute ordering semantics from WHATWG DOM spec, and in general overhaul attribute storage implementation to be much more awesome and accurate. (@lddubeau)
• Add: port and protocol to HTMLAnchorElement. (@sporchia)
• Fix: make HTMLInputElement not have a type attribute by default. It still has a default value for the type property, viz. "text". (@aredridel)
• Fix: treat empty namespace URI as meaning "no namespace" with the getAttributeNS, hasAttributeNS, and setAttributeNS functions. (@lddubeau)
• Fix: reference typed arrays in a way that doesn't immediately break on Node 0.6. Node 0.6 isn't supported in general, though. (@kangax)

• Add: store and use cookies between requests; customizable cookie jars also possible. (@stockholmux)
• Fix: attributes named the same as prototype properties of NamedNodeMap no longer break jsdom. (@papandreou)
• Fix: removeAttributeNS should not throw on missing attributes. (@lddubeau)
• Change: remove __proto__, __defineGetter__, and __defineSetter__ usage, as part of a project to make jsdom work better across multiple environments. (@lawnsea)

• Add: hash property to HTMLAnchorElement. (@fr0z3nk0)

• Upgrade: cssom to 0.3.0, adding support for @-moz-document and fixing a few other issues.
• Upgrade: cssstyle to 0.2.6, adding support for many shorthand properties and better unit handling.

• Fix: avoid repeated NodeList.prototype.length calculation, for a speed improvement. (@peller)

• Add: host property to HTMLAnchorElement. (@sporchia)

• Fix: stop accidentally modifying Error.prototype. (@mitar)
• Add: a dummy getBoundingClientRect method, that returns 0 for all properties of the rectangle, is now implemented. (@F1LT3R)

• Add: href property on CSSStyleSheet instances for external CSS files. (@FrozenCow)

• Add: typed array constructors on the window. (@nlacasse)
• Fix: querySelector and querySelectorAll should be on the prototypes of Element and Document, not own-properties. (@mbostock)

• Fix: when auto-detecting whether the first parameter to jsdom.env is a HTML string or a filename, deal with long strings correctly instead of erroring. (@baryshev)

• Add: basic window.history support, including back, forward, go, pushState, and replaceState. (@ralphholzmann)
• Add: if an <?xml?> declaration starts the document, will try to parse as XML, e.g. not lowercasing the tags. (@robdodson)
• Fix: tag names passed to createElement are coerced to strings before evaluating.

• Fix: a casing issue that prevented jsdom from loading on Unix and Solaris systems. (@dai-shi)
• Fix: window.location.replace was broken. (@dai-shi)
• Fix: update minimum htmlparser2 version, to ensure you get the latest parsing-related bugfixes.

• Add: working XMLHttpRequest support, including cookie passing! (@dai-shi)
• Add: there is now a window.navigator.noUI property that evaluates to true, if you want to specifically distinguish jsdom in your tests.

• Change: the logic when passing jsdom.env a string is more accurate, and you can be explicit by using the html, url, or file properties. This is a breaking change in the behavior of html, which used to do the same auto-detection logic as the string-only version.
• Fix: errors raised in scripts are now passed to jsdom.env's callback. (@airportyh)
• Fix: set window.location.href correctly when using jsdom.env to construct a window from a URL, when that URL causes a redirect. (@fegs)
• Add: a more complete and accurate window.location object, which includes firing hashchange events when the hash is changed. (@dai-shi)
• Add: when using a non-implemented feature, mention exactly what it was that is not implemented in the error message. (@papandreou)

• Fix: custom attributes whose names were the same as properties of Object.prototype, e.g. "constructor", would confuse jsdom massively.

• Fix: CSS selectors which contain commas inside quotes are no longer misinterpreted. (@chad3814)
• Add: <img> elements now fire load events when their src attributes are changed. (@kapouer)

• Fix: better automatic detection of URLs vs. HTML fragments when using jsdom.env. (@jden)

• Fix: URL resolution to be amazing and extremely browser-compatible, including the interplay between the document's original URL, any <base> tags that were set, and any relative hrefs. This impacts many parts of jsdom having to do with external resources or accurate href and src attributes. (@deitch)
• Add: access to frames and iframes via named properties. (@adrianlang)
• Fix: node-canvas integration, which had been broken since 0.5.7.

• Make the code parseable with Esprima. (@squarooticus)
• Use the correct package.json field "repository" instead of "repositories" to prevent npm warnings. (@jonathanong)

Integrated a new HTML parser, htmlparser2, from fb55. This is an actively maintained and much less buggy parser, fixing many of our parsing issues, including:

• Parsing elements with optional closing tags, like <p> or <td>.
• The innerHTML of <script> tags no longer cuts off the first character.
• Empty attributes now have "" as their value instead of the attribute name.
• Multiline attributes no longer get horribly mangled.
• Attribute names can now be any value allowed by HTML5, including crazy things like ^.
• Attribute values can now contain any value allowed by HTML5, including e.g. > and <.

• Fix: make event handlers attached via on<event> more spec-compatible, supporting return false and passing the event argument. (@adrianlang)
• Fix: make the getter for textContent more accurate, e.g. in cases involving comment nodes or processing instruction nodes. (@adrianlang)
• Fix: make <canvas> behave like a <div> when the node-canvas package isn't available, instead of crashing. (@stepheneb)

• Fix: on<event> properties are correctly updated when using setAttributeNode, attributeNode.value =, removeAttribute, and removeAttributeNode; before it only worked with setAttribute. (@adrianlang)
• Fix: HTMLCollections now have named properties based on their members' id and name attributes, e.g. form.elements.inputId is now present. (@adrianlang)

• Fix: readOnly and selected properties were not correct when their attribute values were falsy, e.g. <option selected="">. (@adrianlang)

This release, and all future releases, require at least Node.js 0.8.

• Add: parser can now be set via jsdom.env configuration. (@xavi-)
• Fix: accessing rowIndex for table rows that are not part of a table would throw. (@medikoo)
• Fix: several places in the code accidentally created global variables, or referenced nonexistant values. (@xavi-)
• Fix: <img> elements' src properties now evaluate relative to location.href, just like <a> elements' href properties. (@brianmaissy)

This release is compatible with Node.js 0.6, whereas all future releases will require at least Node.js 0.8.

• Fix: getAttributeNS now returns null for attributes that are not present, just like getAttribute. (@mbostock)
• Change: "request" dependency pinned to version 2.14 for Node.js 0.6 compatibility.

• Fix: stylesheets with @-webkit-keyframes rules were crashing calls to getComputedStyle.
• Fix: handling of features option to jsdom.env.
• Change: retain the value of the style attribute until the element's style property is touched. (@papandreou)

• Fix: selectedIndex now changes correctly in response to <option> elements being selected. This makes <select> elements actually work like you would want, especially with jQuery. (@xcoderzach)
• Fix: checked works correctly on radio buttons, i.e. only one can be checked and clicking on one does not uncheck it. Previously they worked just like checkboxes. (@xcoderzach)
• Fix: click() on <input> elements now fires a click event. (@xcoderzach)

• Fix: Make contextify a non-optional dependency. jsdom never worked without it, really, so this just caused confusion.

• Fix: selected now returns true for the first <option> in a <select> if nothing is explicitly set.
• Fix: tweaks to accuracy and speed of the querySelectorAll implementation.

• Fix: crashes when loading HTML files with <a> tags with no href attribute. (@eleith)