This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Firefox doesn't recognize file://~?

  • 2 răspunsuri
  • 1 are această problemă
  • 17 vizualizări
  • Ultimul răspuns de cor-el

more options

When I type / in the address bar Firefox immediately realizes that it's a local path and suggests file:///. But neither ~ nor file://~ points to my home directory. I hope Firefox will recognize ~ and save me from typing /home/my_username in the address bar myself.

When I type / in the address bar Firefox immediately realizes that it's a local path and suggests file:///. But neither ~ nor file://~ points to my home directory. I hope Firefox will recognize ~ and save me from typing /home/my_username in the address bar myself.

Modificat în de sw

Soluție aleasă

Hi, Firefox is actually governed by standards here, and they explicitly call out that `~` expansion isn't supported in file:// URIs:

https://tools.ietf.org/html/rfc8089#appendix-D.1

Unfortunately, I doubt there is much that can be done about that - it isn't a common feature across all operating systems, which is probably why the RFC has specified it in that manner.

Citește acest răspuns în context 👍 1

Toate răspunsurile (2)

more options

Soluție aleasă

Hi, Firefox is actually governed by standards here, and they explicitly call out that `~` expansion isn't supported in file:// URIs:

https://tools.ietf.org/html/rfc8089#appendix-D.1

Unfortunately, I doubt there is much that can be done about that - it isn't a common feature across all operating systems, which is probably why the RFC has specified it in that manner.

more options

A possible workaround is to use a keyword (fh) bookmark that adds the file path.

  • file:////home/my_username/%s