On 23/01/2024 19:30, Greg Wooledge wrote:
Also from the "weird results" category: if I mangle the URL by using two slashes instead of three, Chrome appears to treat that as a relative pathname, attempts to open usr/share/whatever instead of /usr/share/whatever, fails, and gives me an error page.
Formally with 2 slashes it might be treated file://hostname/path https://www.freedesktop.org/wiki/Specifications/file-uri-spec/ https://www.rfc-editor.org/rfc/rfc1738#section-3.10Qt (unrelated to chromium) might do some funny things with the component after 2 slashes for arbitrary protocols, e.g. to downcase it.