Re: [whatwg/url] Inconsistency in Handling `special-scheme-missing-following-solidus` URLs (Issue #822)

> 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]](https://url.spec.whatwg.org/#biblio-rfc3986) [[RFC3987]](https://url.spec.whatwg.org/#biblio-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](https://url.spec.whatwg.org/#special-scheme-missing-following-solidus)
> 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



-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/822#issuecomment-1936125438
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/822/1936125438@github.com>