Dušan Maliarik

The `DOMParser-fromString` change IMO is fully backwards compatible, I've only seen it (`(DOMParser.)`) used in public `parse` function where I replaced it with single `DOMParser-fromString` call, that either uses browsers...

@jeluard I see it now, `wholeText` seems to be present in the output of `DOMParser`, but it isn't available on the DOM found directly in the browser. Eg. when you...

Unfortunately `jsdom` is the only viable option so far, the only one exposing (exporting) constructors for `NodeList`, `Node` and `NamedNodeMap`. Another thing is that is uses `AttributeList` for `node.attributes`. We'd...

Ok, so is `(or (aget this "wholeText") (aget this "nodeValue"))` acceptable in both `as-hickory` and `as-hiccup`? About the `jsdom` / `polyfill` issue, is the current solution in this pull request...

I think so, but that would mean doing the `require`ing and `if`s all at the runtime, every time you call to `parse`, instead of just once during the load time,...

I did so over [here](https://groups.google.com/forum/#!topic/clojurescript/rqGBlKc3SXI). Additionally I have to use this line to have it working with `master` ``` clojure (js/Object.defineProperty (.-prototype Text) "wholeText" #js {:get (fn [] (js* "this.nodeValue"))})...

Indeed jsdom looks like you can actually use `extend-type`, when you do a deep require (eg. `require("jsdom/lib/jsdom/level1/core").dom.level1.NodeList`)

This seems to work thanks to a well structured code in both `hickore.core` and `jsdom`. I can now use the same parser on both platforms that I target with the...

@sritchie I ditched `jsdom` because it was too slow, and ended up writing small wrapper around `node-libxml`. I found that hickory only uses a few DOM methods, so as long...

@hzhu Because there's no `implementation` property on `document` object. Feel free to fork `libxml-dom` and send in a PR. I might do this myself but can't give you any estimate.