Has anyone ever done experiments on alternative URL input fields? We continue to treat URLs as arbitrary strings, although they are composed of very well define

Has anyone ever done experiments on alternative URL input fields? We continue to treat URLs as arbitrary strings, although they are composed of very well defined components, say for `https://foo:bar@news.ycombinator.com/item?id= https://foo:bar@news.ycombinator.com/item?id= 31820149#31821636`: - Transfer protocol (https://) - Optional credentials (foo@ or foo:bar@) - Mandatory hostname (news.ycombinator.com) - Optional path name (/item) - Optional parameters as key-value pairs (id=31820149) - Optional document anchor (#31821636) This is easily imaginable as a form, even if that would obviously by inconvenient. It feels to me like there is a middle ground between "enter every URL part into a separate input box" and "let users handle an arbitrary serialisation format completely on their own".