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

Still No Print!?!? Jan 2022, vers. 96 for Android.

  • 3 odgovori
  • 2 ima ovaj problem
  • 1 view
  • Posljednji odgovor poslao a+firefox.com

more options

Why has the option to print STILL not been added back in? (January 2022, version 96 for Android) Why was it removed to begin with? Seems like a key feature for a lot of people. No plugins or add-ons for it either. Once I switch, I won't be back.

Why has the option to print STILL not been added back in? (January 2022, version 96 for Android) Why was it removed to begin with? Seems like a key feature for a lot of people. No plugins or add-ons for it either. Once I switch, I won't be back.
Priloženi snimci ekrana

All Replies (3)

more options

Hi

Thank you for your feedback. This is something that our developers are aware of and are looking into. You can follow progress on this and add comments at:

https://github.com/mozilla-mobile/fenix/issues/10217

more options

I'm gone. They soured a longtime user. And to get me upset enough to quit on something after the last two years?....that's impressive.

Even more disheartening is the lack of response other than a Hey we hear you, Buddy, and, Ya know Sport, we want you to know we've taken everything under advisement.

Zero info. No why, no when. It they can't/won't even give any kind of a broadstroke timeframe means there isn't one because it's not even being looked at right now.

It's weird having something other than Firefox as my default browser. Sad. I'll be back when you guys get right, maybe, I might just have fallen for another "browser next door" as long as it has taken. So hurry up and fix it. I want you to be my "browser next door'.

In hopes I can default to you soon, I'm much obliged. Thank you.

GiarcO O.

more options

This is STILL an issue? It's been years, folks. It was a feature that existed in FF before -- it can't be *that* hard to port the code to the new codebase...

I know, I know -- if I really cared, I'd get in there and fix it myself...

But still, it's hard, with how borked the new Android version is, to not suspect that Google, Micro$oft, Dr. Evil, etc. is influencing the development directions to ensure that FF never again becomes a dominant browser...