*Permananently Deleted*
Mozilla Closes Request to Restore Full URLS on Fenix, Will Not Fix

Link to the recent feature request to restore the full URL…

Permananently Deleted


What a cynical fucking post. I think, the default is absolutely sensible, because yes, most phones have very limited horizontal space and being able to read more of the end rather than “https://www” is more useful to most users.

Besides, you can find out the full URL by tapping into the URL bar or the padlock (the latter also indicates https or http).

I would absolutely support having an option for this, but it doesn’t seem to be that easy to actually implement. Because adding a UI toggle for this requires it being translated into the however many languages they support, and about:config only works for Gecko-related stuff, not for the Fenix UI.


I just checked, and when you click on it, it also shows the full URL. Are people really just complaining about showing a shortened url for tabs in mobile?

People love to nitpick Firefox.


That’s what I got from it, yeah.

I myself am not enamored by Apple’s and Google’s policy of “Users don’t understand URLs, so let’s hide them away”, because I really don’t think that makes it any easier to understand (and they probably don’t actually want users to understand).

And then presumably these complaints stem from the fear that Mozilla will follow their example and stop showing any useful information in the URL bar.
But I really think this is unjustified. With the limited horizontal space, hiding the less relevant parts of the URL actually helps to see the more relevant parts. So, this design choice achieves the opposite of what they’re afraid of.


I would absolutely support having an option for this, but it doesn’t seem to be that easy to actually implement. Because adding a UI toggle for this requires it being translated into the however many languages they support, and about:config only works

Agreed that it should be a preference, but disagree on localization being justification for not implementing it. Localization should be part of the preference system design and if it is that big of a problem to localize, then there are bigger issues at FF. This is a URL transparency issue imo, not one of language.


I’m not saying that localization is justification for not including it. I’m saying that, as far as I’m aware, it’s pretty much a non-issue, since I struggle to think of a scenario where you need to see the “www”, and because you can very easily view the full URL, if you need to.

And then I’m saying that I would support including an option, because I might not know all use-cases. However, if it costs more than a few minutes to include such an option, then I would like to see an actual argument for it first, not just the possibility of it being useful.
I would frankly consider it irresponsible, if Mozilla invested donation and/or Google money without putting that into question. On the other hand, if the wider open-source community contributed this, that would be fine, again.

Finally, please don’t call your viewpoint “URL transparency” in this. I consider it a much bigger URL transparency issue, if the user could visit “https://www.wikipedia.org.hackerdomain.com” without knowing, because the URL got cut off on their small phone screen.
Like, that’s an actual security problem, allowing for phishing and similar, whereas not being able to see the subdomain, when it’s “www”, that should still keep you on the same domain and therefore not be a major security problem.


Thank you for elaborating, I understand where you are coming from, it seems like a non issue so any effort required to roll it back should be better spent elsewhere. I don’t think this would be a big component of anti-phishing feature, nor a localisation problem. The argument is basically: theres nothing wrong with it, don’t waste time on those who disagree.

If you have run your phone through a local proxy like squid or otherwise logged your traffic, you know that the amount of mixed http / https content being shoved through mobile browsers is lamentable. Without the ability to have extensions like https everywhere, ublock etc, it is nearly impossible for users to block this. Being able to clearly see the protocol and fully qualified domain is one piece of information that can help.

Furthermore, any trend toward users not needing to know where they are and letting technology companies craft the location UX is another step closer to technology tyranny.


I don’t like it either that we’re “dumbing down” the UI and basically hiding information from users out of fear that they might be confused by it, because I really think it’s more confusing to sometimes show all of it and sometimes not.
I just think, it’s positive to hide it in this case, because it’s very important that the top-level domain is fully visible and because there is limited horizonal space.

And well, you can still tell https and http apart by looking at the padlock.
I’m also not sure, if this is what you meant, but you can install HTTPS Everywhere and uBlock Origin in the new Android Firefox. They don’t have a lot of extensions working yet, but those two are among the ones that are available.


As a tech giant skeptic (with ff being the new york to googles california in terms of policy adoption), I see a possible extension of address modification trends: just remove the address all together and replace it with the favicon and page title. major browsers introduce a verified favicons service, which is a board of experts which determines if the site is safe. verified favicons are served from by a central verified favicon server which takes your fingerprint when accessing or serves you a captcha, or denies access. If your sites favicon is not verified, browsers replace your favicon with a nuclear hazard favicon

I doubt this is the exact outcome, but internet as intranet with authorized portals and services dictating user browsing experience is not far from a technocratic dream.

A place to discuss the news and latest developments on the open-source browser Firefox

  • 0 users online
  • 2 users / day
  • 13 users / week
  • 61 users / month
  • 150 users / 6 months
  • 1556 subscribers
  • 156 Posts
  • Modlog