Inconsistency in Handling `special-scheme-missing-following-solidus` URLs about url

[annevk]

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]

Align RFC 3986 and RFC 3987 with contemporary implementations and obsolete the RFCs in the process. (E.g., spaces, other "illegal" code points, query encoding, equality, canonicalization, are all concepts not entirely shared, or defined.) URL parsing needs to become as solid as HTML parsing. [RFC3986] [RFC3987]

I have tried to report this issue to some browsers, and here is what I got

Mozilla

From https://bugzilla.mozilla.org/show_bug.cgi?id=1879227

Me: Okay, but I still think it’s an issue, maybe with WhatWG. I’ll ask them and find out. Thank you
Mozilla: I agree. The URL is parsed according to the URL standard
Mozilla: This specific case would be a validation error, but either way the parsing is correct and all browsers agree on this behaviour.

From that snippet, in my opinion, it is unclear whether they agree or disagree on this, as they said that the parsing is correct and all browsers agree on this behaviour., but they also said "I agree" when I was referring to this behavior as an issue

Chromium

I tried to report it through Chromium's issue tracker, but I can't see the current status of my bug report

[annevk]

I think Valentin agreed with Tom there, not with you.

[RedYetiDev]

You're probably right. What does this mean for this bug report?

[annevk]

I'll close it as this is not something we want to change. Thanks for taking the time to report it!