LayoutTests/fast/forms/ValidityState-typeMismtch-url.html fails on Chromium port because KURL implementation in Chromium is different from other ports, and host name validation rules are mismatched between the normal KURL and Chromium KURL. > FAIL http://www.g**gle.com is an incorrect valid url. > FAIL http:// www.google.com is an incorrect valid url. > FAIL http://www .google.com is an incorrect valid url. > FAIL http://www.&#10;google.&#13;com is an incorrect valid url. > FAIL http://host+ is an incorrect valid url. > FAIL http://myurl! is an incorrect valid url. The ASCII host name rule in the normal KURL is like: HEXDIG = "0-9A-Fa-f" KURL_IPV6ADDR = "[" + HEXDIG + ":]+" ALPHADIGIT = "0-9A-Za-z" KURL_HOST = "¥¥[" + KURL_IPV6ADDR + "]|[-._" + ALPHADIGIT + "]*" The ASCII host name rule in Chromium KURL, GoogleURL, is like: PCT_ENCODED = "%[" + HEXDIG + "]{2}" GURL_HOST = "(" + PCT_ENCODED + "|[- !"#$&'()*+,.:<=>@[]_`{|}" + ALPHADIGIT + "])*" HTML5's URL type is an absolute URI or an absolute IRI. URI (RFC3986)'s host name rule is like: IPV6ADDR = "[" + HEXDIG + ":.]+" UD = "-!$&'()*+,.;=_~" + ALPHADIGIT IPADDR = "(" + IPV6ADDR + "|v[0-9]¥.[:" + UD + "]+)" URI_HOST = "¥¥[" + IPADDR + "]|(" + PCT_ENCODED + "|[" + UD + "])*" IMO, - Changing GoogleURL so that it has the same rules as KURL - Changing KURL so that it has the same rules as GoogleURL - Changing both of GoogleURL and KURL so that they are compliant to the standards strictly They DON'T work well because I think KURL and GoogleURL have practical reasons of the non-standard rules. Should we have dedicated URL validator for <input type=url>? In that case, how to check IDN validity?