We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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.

Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

Why does FF have such poor design?

  • 2 vastausta
  • 1 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja webistrator

webistrator
webistrator
more options

Only after committing to installing FF8 does one find out that their needed add-ons will not work. This could be checked by simply analyzing the current FF installed and THEN ADVISING the user that their trusted add-ons are not going to work.

But no...FF in it's MS-like stupidity, only advises of inoperability AFTER one installs FF8.

So for me, after five years of FF, I'm going to Chrome where the understand software user interface design.

Kiss mine, FF!

Oh, but wait...the "Submit Feedback" doesn't even work correctly -- typical FF!!!

Edited by a moderator due to language. See the Rules & Guidelines .

Only after committing to installing FF8 does one find out that their needed add-ons will not work. This could be checked by simply analyzing the current FF installed and THEN ADVISING the user that their trusted add-ons are not going to work. But no...FF in it's MS-like stupidity, only advises of inoperability AFTER one installs FF8. So for me, after five years of FF, I'm going to Chrome where the understand software user interface design. Kiss mine, FF! Oh, but wait...the "Submit Feedback" doesn't even work correctly -- typical FF!!! ''Edited by a moderator due to language. See the [http://support.mozilla.com/kb/Forum+and+chat+rules+and+guidelines Rules & Guidelines] .''

Muokattu , muokkaaja the-edmeister

Valittu ratkaisu

Before I retired, I worked in software and interface design for nearly 40 years. Never...I repeat, NEVER was upward (i.e. new release) compatibility verification an "add-on" afterthought. But as a dev. manager I did have to deal with other designers and developers who thought such user-friendly "niceties" were unnecessary. "They'll figure it out...", etc., was the mindset.

Clearly, someone else had the interest to create some way to test FF upward compatibility. But who's to know one has to go and find it as an add-on??? I'm bombarded with pop-up admonitions to "update to the latest and greatest FF8..." and nary a word is said about "...but you'd better check to see if we support (e.g.) Google toolbar, Interclue, Lazarus, etc., etc., etc. Why? A simple extraction of a user's install. configuration could be fed back to the FF DB, tested and a msg. sent back saying, "Go ahead, install. But you'll lose the following add-on functionality until they are made compatible:

1. 2. . . ."

But OK -- those folks have to "catch up" to FF8. Let them decide whether to install or not.

But what do I know, right? I'm just a user. And we all know users are stupid by nature; otherwise, they'd develop clever software... . And this is the problem with software development today: the user is treated like an idiot and doesn't know what's good for him/her.

But thanks for fielding that rant. I just wish the people who make these messes would read these things.

W.

Lue tämä vastaus kontekstissaan 👍 0

Kaikki vastaukset (2)

David McRitchie
David McRitchie
more options

The "*Is It Compatible?" extension will tell you about what you have installed, whether it is compatible or not. If not compatible you will have to investigate the versions available, the developer comments and the user comments at addons.


Feedback for extensions...

Feedback is more for those doing beta testing, but it was a one way feedback. The system has improved in that you can test in beta, and report whether an extension works or not, the only problem is that you can only provide a short message if there is a problem, not if you solved a problem and are running fine.
webistrator
webistrator Kysymyksen kysyjä
more options

Valittu ratkaisu

Before I retired, I worked in software and interface design for nearly 40 years. Never...I repeat, NEVER was upward (i.e. new release) compatibility verification an "add-on" afterthought. But as a dev. manager I did have to deal with other designers and developers who thought such user-friendly "niceties" were unnecessary. "They'll figure it out...", etc., was the mindset.

Clearly, someone else had the interest to create some way to test FF upward compatibility. But who's to know one has to go and find it as an add-on??? I'm bombarded with pop-up admonitions to "update to the latest and greatest FF8..." and nary a word is said about "...but you'd better check to see if we support (e.g.) Google toolbar, Interclue, Lazarus, etc., etc., etc. Why? A simple extraction of a user's install. configuration could be fed back to the FF DB, tested and a msg. sent back saying, "Go ahead, install. But you'll lose the following add-on functionality until they are made compatible:

1. 2. . . ."

But OK -- those folks have to "catch up" to FF8. Let them decide whether to install or not.

But what do I know, right? I'm just a user. And we all know users are stupid by nature; otherwise, they'd develop clever software... . And this is the problem with software development today: the user is treated like an idiot and doesn't know what's good for him/her.

But thanks for fielding that rant. I just wish the people who make these messes would read these things.

W.