I'm not too keen into adding workarounds for system misconfigurations unless they are knowingly common among our users. Honestly I don't think having a "localhost" protocol registered is so common. The benefit seems extremely thin in this case, compared to things like bug 1220810 that surely affects a wider population. (In reply to :Gijs (he/him) from comment #7) > That would only fix localhost, but not the generic problem. bug 1744243 has what I think is a more thorough suggestion - though perhaps we still need a refinement in that bug to navigate to `http://` + input (rather than searching) for input matching `[a-z.0-9-]+:[0-9]+` or w/e. I suspect it will just work if the host is in browser.fixup.domainwhitelist.* and localhost is there by default.
Bug 1697768 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'm not too keen on adding workarounds for system misconfigurations unless they are knowingly common among our users. Honestly I don't think having a "localhost" protocol registered is so common. The benefit seems extremely thin in this case, compared to things like bug 1220810 that surely affects a wider population. (In reply to :Gijs (he/him) from comment #7) > That would only fix localhost, but not the generic problem. bug 1744243 has what I think is a more thorough suggestion - though perhaps we still need a refinement in that bug to navigate to `http://` + input (rather than searching) for input matching `[a-z.0-9-]+:[0-9]+` or w/e. I suspect it will just work if the host is in browser.fixup.domainwhitelist.* and localhost is there by default.