srcipt src strangeness about jsdom

[automatthew]

You'll want to tell jsdom the document location. Level can be left null:

jsdom.jsdom(slashDotContent, null, urlOfDoc).createWindow();

[tmpvar]

I think the actual parsing of hrefs/srcs is not robust enough to handle this case. Initially I thought aa492e2 would fix this problem, but I believe it would simply produce a relative url in the case of a //domain.tld/path/to/resource. Thank you for noticing this and submitting this issue. We'll address this shortly.

[aflatter]

I actually just worked on this because I had some problems with paths like '/foo.js' which have overriden the baseUrl. This has been fixed with: aflatter/jsdom@bc6de0b

Additionally the slashdot issue is fixed with: aflatter/jsdom@aa9de67
Reading the RFC, I don't really know if you can assume 'http' though.

An ugly test is at https://gist.github.com/feabb0152d953ed7ef51 - I was not sure where to expand your test suite.

[aflatter]

We just found out that my fix is actually wrong. Try the following snippet in your favorite browser from a https url:

y = document.createElement('a'); y.setAttribute('href', '//foo.com/bar'); y.href
=> "https://foo.com/bar"

Fix will follow :)

[aflatter]

Committed to my fork (https://github.com/aflatter/jsdom/tree/level2_resources).

Still, there are some questions. If we can not determine the base url it is not possible to determine the path for relative hrefs. We gotta think about how to handle these.

[tmpvar]

this has been thoroughly tested here: https://github.com/tmpvar/jsdom/blob/master/test/jsdom/index.js#L403