According to RFC 3966 (The tel URI for Telephone Numbers, http://tools.ietf.org/html/rfc3966), forward slashes after the scheme are not valid syntax. So QUrl’s parser is right to reject them. In contrast, GURL has a custom parser (based on third-party code from mozilla) which, for all non-standard schemes (kStandardURLSchemes), always considers the host empty.
We could probably write a custom GURL->QUrl converter with added logic to parse valid GURLs that produce invalid QUrls.
According to RFC 3966 (The tel URI for Telephone Numbers, http:// tools.ietf. org/html/ rfc3966), forward slashes after the scheme are not valid syntax. So QUrl’s parser is right to reject them. In contrast, GURL has a custom parser (based on third-party code from mozilla) which, for all non-standard schemes (kStandardURLSc hemes), always considers the host empty.
We could probably write a custom GURL->QUrl converter with added logic to parse valid GURLs that produce invalid QUrls.