Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

تلاش سپورٹ

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.

مزید سیکھیں

Firefox doesn't recognize file://~?

  • 2 جواب دیں
  • 1 میں یہ مسئلہ ہے
  • 17 دیکھیں
  • آخری جواب بذریعہ 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.

sw کی جانب سے میں ترمیمکی گئ

منتخب شدہ حل

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.

اس جواب کو سیاق و سباق میں پڑھیں 👍 1

تمام جوابات (2)

more options

منتخب شدہ حل

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