Revision fee987632e670876c7468ccd695f41fe90911d6b authored by Manuel Rego Casasnovas on 05 April 2018, 07:04:59 UTC, committed by Manuel Rego Casasnovas on 05 April 2018, 07:04:59 UTC
The CSSWG resolved to make it explicit in the spec in issue w3c/csswg-drafts#2145. The reason is that there's interop between all UAs regarding this. These 2 tests were marked as optional "may" but they're not optional anymore.
1 parent 54f844c
README.md
These tests are for browsers, but the data for
`a-element.html`, `url-constructor.html`, and `a-element-xhtml.xhtml`
is in `urltestdata.json` and can be re-used by non-browser implementations.
This file contains a JSON array of comments as strings and test cases as objects.
The keys for each test case are:
* `base`: an absolute URL as a string whose [parsing] without a base of its own should succeed.
This key is always present,
and may have a value like `"about:blank"` when `input` is an absolute URL.
* `input`: an URL as a string to be [parsed][parsing] with `base` as its base URL.
* Either:
* `failure` with the value `true`, indicating that parsing `input` should return failure,
* or `href`, `origin`, `protocol`, `username`, `password`, `host`, `hostname`, `port`,
`pathname`, `search`, and `hash` with string values;
indicating that parsing `input` should return an URL record
and that the getters of each corresponding attribute in that URL’s [API]
should return the corresponding value.
The `origin` key may be missing.
In that case, the API’s `origin` attribute is not tested.
[parsing]: https://url.spec.whatwg.org/#concept-basic-url-parser
[API]: https://url.spec.whatwg.org/#api
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...