Closed Bug 291258 Opened 20 years ago Closed 19 years ago

Protect newbie-users from plug-in-problems after FF update/upgrade

Categories

(Firefox :: General, defect)

defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: raoul.teeuwen, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Hello.

I have read & heard of several FF-users having problems after installing a new
FF-version. Those problems often are caused by plug-ins. But newbie-users don't
detect this, blame FF, turn away from FF and spread bad info to potential others.

I can understand the FF-team can't be responsible for plug-ins. But maybe there
is a simple solution to solve potential problems. Like displaying a big warning
message every time a new version boots for the 1st time. Or by default boot
without plug-ins for the 1ste time after every (minor and major) FF-update.

My sole intention is preventing people to turn away from FF while actually the
problems those users experience are not caused by FF...

I started a question in Mozillazine, but was pointed to bugzilla. My original
question: http://forums.mozillazine.org/viewtopic.php?p=1403726#1403726 .

Kindest regards,

Raoul.

Reproducible: Sometimes

Steps to Reproduce:
Depends on plug-ins being installed and whether they conflict with a new FF-version.
Actual Results:  
I had people report FF going blank etc

Expected Results:  
Exclude all plug-ins on 1st boot?
Flags: blocking-aviary1.1+
Flags: blocking-aviary1.1+
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.