annevk
commented
7 months ago This is a very well written issue report, however, I'm afraid that the request goes counter to one of our goals: https://url.spec.whatwg.org/#goals. In particular getting alignment across implementations. This change would likely not be web compatible and lead to broken experiences for end users.
(Apologies if browsers match what you propose and you just forgot to write that down. I'm pretty sure they don't, but I didn't double check.)
RedYetiDev
What is the issue with the URL Standard?
Description:
The current implementation of the WhatWG URL standard exhibits inconsistency in handling
special-scheme-missing-following-solidusURLs, leading to unexpected behavior and discrepancies across various scenarios. This bug report aims to elucidate the issue and propose a standardized approach for handling such URLs to enhance consistency and predictability.Current Behavior:
The handling of
special-scheme-missing-following-solidusURLs is outlined in the provided table:http://example.com/http:web.sitehttp://example.com/web.sitehttp://example.com/https:web.sitehttps://web.site/https://example.com/http:web.sitehttp://web.site/https://example.com/https:web.sitehttps://example.com/web.siteIssue:
The existing handling of
special-scheme-missing-following-solidusURLs results in inconsistencies, particularly when the URL scheme differs from the base URL scheme. For example, in the second row of the table, the resulting URL ishttps://web.site/, which may not align with user expectations.Suggested Improvement:
To standardize and enhance predictability, I propose adopting one of the following approaches:
Consistent Domain Resolution:
Ensure that the resolved URL consistently reflects the domain specified in the input, irrespective of the base URL scheme. This approach fosters consistency across diverse scenarios and mitigates unexpected outcomes.
Revised Table:
http://example.com/http:web.sitehttp://web.sitehttp://example.com/https:web.sitehttp://web.site/https://example.com/http:web.sitehttp://web.site/https://example.com/https:web.sitehttps://web.sitePreserve Base Domain:
Ensure that the resolved URL incorporates the base domain when the input URL does not explicitly specify it. This approach maintains clarity regarding the base domain and yields predictable outcomes when the domain is omitted in the input URL.
Revised Table:
http://example.com/http:web.sitehttp://example.com/web.sitehttp://example.com/https:web.sitehttp://example.com/web.site/https://example.com/http:web.sitehttps://example.com/web.site/https://example.com/https:web.sitehttps://example.com/web.siteConclusion:
Standardizing the handling of
special-scheme-missing-following-solidusURLs will bolster consistency, predictability, and interoperability across various implementations of the WhatWG URL standard. The proposed improvements aim to rectify the existing inconsistency and ensure a more coherent behavior in URL resolution.