- From: Domenic Denicola <web-platform-tests-notifications@w3.org>
- Date: Fri, 15 Apr 2016 22:50:03 GMT
- To: public-web-platform-tests-notifications@w3.org
OK, I found one bug in our scheme parsing state. The remaining list of things where either jsdom/whatwg-url has a bug or the spec is not matched, accounting for the failure to distinguish throwing setters from no-ops as mentioned above, is these four: ``` <http://example.net>.protocol = "b" Spec deviation: from special scheme to not is not problematic. https://github.com/whatwg/url/issues/104 <ssh://me@example.net>.protocol = "http" Spec deviation: from non-special scheme with a host to special is not problematic. https://github.com/whatwg/url/issues/104 <http://example.net:8080>.host = "example.com:" Port number is removed if empty in the new value: https://github.com/whatwg/url/pull/113 <http://example.net:8080>.port = "" Port number is removed if empty in the new value: https://github.com/whatwg/url/pull/113 ``` I count two spec deviations plus the problem I mentioned above where I can't find where in the spec the port number is removed if empty is the new value. View on GitHub: https://github.com/w3c/web-platform-tests/pull/2830#issuecomment-210673812
Received on Friday, 15 April 2016 22:50:10 UTC