საიტის გასაუმჯობესებელი სამუშაოების მიმდინარეობისას, შესაძლებლობების ნაწილი შეიზღუდება. თუ სტატიით ვერ მოახერხებ ხარვეზის გამოსწორება და შეკითხვის დასმა გსურთ, ჩვენი მხარდაჭერის გუნდი დაგეხმარებათ @FirefoxSupport გვერდის მეშვეობით Twitter-ზე და /r/firefox განყოფილებაში Reddit-ზე.

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

Mozilla/Firefox needs a clear policy guideline for updates: a promise to users. How about it?

  • 1 პასუხი
  • 1 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 1 ნახვა
  • ბოლოს გამოეხმაურა the-edmeister

Why doesn't Mozilla/Firefox draft a policy guideline for updates, and then stick to it as a promise to the average everyday user? This would avoid a lot of unnecessary anger and time-wasting while users are left to try to find out WTF is going on and get their options back the way they like. This guideline would include basic things such as (1) "If it ain't broke, we won't fix it." (2) "New features will be explained FIRST and provided as an opt-in, not as an opt-out default." (3) "Compatability with add-ons, apps and extensions will be checked BEFORE updates are installed and the user given a warning AND a choice as to whether to update or not." (4) "Changes to the interface will be provided as an opt-in, not as an opt-out default." (5) "If a new feature is devised and it is basically an add-on (such as Pocket), it will be available for integration with Firefox only as an add-on, app or extension (perhaps with a short notice explaining its availability following a successful update install)."

Why doesn't Mozilla/Firefox draft a policy guideline for updates, and then stick to it as a promise to the average everyday user? This would avoid a lot of unnecessary anger and time-wasting while users are left to try to find out WTF is going on and get their options back the way they like. This guideline would include basic things such as (1) "If it ain't broke, we won't fix it." (2) "New features will be explained FIRST and provided as an opt-in, not as an opt-out default." (3) "Compatability with add-ons, apps and extensions will be checked BEFORE updates are installed and the user given a warning AND a choice as to whether to update or not." (4) "Changes to the interface will be provided as an opt-in, not as an opt-out default." (5) "If a new feature is devised and it is basically an add-on (such as Pocket), it will be available for integration with Firefox only as an add-on, app or extension (perhaps with a short notice explaining its availability following a successful update install)."

ყველა პასუხი (1)

You may provide feedback to Mozilla here: https://input.mozilla.org/en-US/feedback

For the most part, the support contributors who provide support here are just other users, and many of us may feel like you do about those exact items - as I do.

My own personal responses:

  1. A matter of opinion.
  2. You need to signup for the blog postings where new upcoming features are announced. Or keep up with the development channel versions to "see what is coming down the pike in the next version". example being - https://blog.mozilla.org/futurereleases/2015/07/02/what-to-look-forward-to-from-firefox/
  3. no comment
  4. Is that about Firefox 29 and Australis which happened 15 months ago?
  5. I agree 100% .

"(perhaps with a short notice explaining its availability following a successful update install)" - Like this? https://www.mozilla.org/en-US/firefox/39.0/releasenotes/