This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The expected result for fn-resolve-uri-4 assumes that "http://" is not a valid URI. However, I suppose it is valid according to both RFC 3986 and RFC 2396. Specically, the both RFCs allow authority component to be empty. For example in RFC 3986 we read: authority = [ userinfo "@" ] host [ ":" port ] host = IP-literal / IPv4address / reg-name reg-name = *( unreserved / pct-encoded / sub-delims ) Here '*' means zero-or-more and '[ smth ]' means optional.
A fix has been attempted in CVS, XQTS_current.zip is updated. If the resolution is satisfactory, feel free to change status to CLOSED, otherwise reopen this report. If no feedback is returned within two weeks, this report will automatically be closed. Thanks for reporting!
Thanks for fix. It works now )).