Should file://example%/ fail?

[Gallaecio]

I have written a Python implementation of the URL living standard, and I am now aiming to test it against urltestdata.json.

I have found a test case which I suspect is out of date with regards to the URL living standard:

wpt/url/resources/urltestdata.json

Lines 1081 to 1085 in f119ebc

	{
	"input": "file://example%/",
	"base": "about:blank",
	"failure": true
	},

I believe this input is not supposed to cause a failure since this change in the URL living standard, which, if I am understanding the wording correctly, made it so that host parsing for the file schema is done with isNotSpecial=true, meaning the host here no longer needs to be a valid domain name (which does not support %), but a valid host name (which does support %).

Some other test cases seem to be in a similar situation, such as a few of these:

wpt/url/resources/urltestdata.json

Lines 5804 to 5838 in f119ebc

	{
	"input": "file://%43%3A",
	"base": "about:blank",
	"failure": true
	},
	{
	"input": "file://%43%7C",
	"base": "about:blank",
	"failure": true
	},
	{
	"input": "file://%43|",
	"base": "about:blank",
	"failure": true
	},
	{
	"input": "file://C%7C",
	"base": "about:blank",
	"failure": true
	},
	{
	"input": "file://%43%7C/",
	"base": "about:blank",
	"failure": true
	},
	{
	"input": "https://%43%7C/",
	"base": "about:blank",
	"failure": true
	},
	{
	"input": "asdf://%43|/",
	"base": "about:blank",
	"failure": true
	},

wpt/url/resources/urltestdata.json

Lines 8127 to 8142 in f119ebc

	"Empty host after the domain to ASCII",
	{
	"input": "file://\u00ad/p",
	"base": "about:blank",
	"failure": true
	},
	{
	"input": "file://%C2%AD/p",
	"base": "about:blank",
	"failure": true
	},
	{
	"input": "file://xn--/p",
	"base": "about:blank",
	"failure": true
	},

[Gallaecio]

I think I have misunderstood the standard. When it says “with url is not special”, it must mean “with the isNotSpecial parameter set to the value of url’s isNotSpecial attribute”.