As it stands today, the spec has issues when considering other pre-existing options and future compatibility. For example, there is no way to get the URL if th

As it stands today, the spec has issues when considering other pre-existing options and future compatibility. For example, there is no way to get the URL if the protocol is `file://`. For a real world example: https://github.com/mozilla/standards-positions/issues/194#issuecomment-1220996568 https://github.com/mozilla/standards-positions/issues/194#is... See the stack overflow issue: https://stackoverflow.com/questions/67039633/get-the-text-fragment-part-of-current-url-from-window-location/73366996#73366996 https://stackoverflow.com/questions/67039633/get-the-text-fr... (See also the currently "conflicting" library for URL fragment queries: https://github.com/Cyphrme/URLFormJS https://github.com/Cyphrme/URLFormJS) I think it can be easily fixed, using solutions like a delimiter, but that discussion probably needs to be apart of a wider discussion concerning URL extensibility.