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.

Avatar for Username

Search Support

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.

Learn More

This thread was archived. Please ask a new question if you need help.

MacOs Text replacecements not working in Firefox

  • 3 replies
  • 0 have this problem
  • 2 views
  • Last reply by TyDraniu

dennisa1
dennisa1
more options

The OS-wide feature for MacOS, text replacements does not work in Firefox. The replacements are great time-saving for me and for everyone who works with forms a lot.

This feature is the reason why I avoid using FF, my experience becomes very limited. Safari, Chrome and Opera all have this feature enabled.

Can this be enabled in FF?

The OS-wide feature for MacOS, text replacements does not work in Firefox. The replacements are great time-saving for me and for everyone who works with forms a lot. This feature is the reason why I avoid using FF, my experience becomes very limited. Safari, Chrome and Opera all have this feature enabled. Can this be enabled in FF?

All Replies (3)

TyDraniu
TyDraniu
  • Top 25 Contributor
more options

It can't be enabled right now.

You can try out extensions, for instance:

dennisa1
dennisa1 Question owner
more options

This extentions are not really suitable, because I will have keep 2 seperate lists with all the replacements: for MacOs an Firefox. Moreover the first one is buggy, it does not support even non-latin charaters.

Why can't this be implemented? Every other browser supports it

TyDraniu
TyDraniu
  • Top 25 Contributor
more options

Of course it can be implemented, Devs are working on it under bug 1149826.

See Bugzilla etiquette before commenting in bug reports.