Bug 456254 - Firefox about:config 'void warranty' page NEEDS TO GO AWAY
Summary: Firefox about:config 'void warranty' page NEEDS TO GO AWAY
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: firefox
Version: 5.2
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Gecko Maintainer
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 456301
TreeView+ depends on / blocked
 
Reported: 2008-07-22 14:34 UTC by Suzanne Hillman
Modified: 2012-05-04 10:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-04 10:15:32 UTC
Target Upstream Version:


Attachments (Terms of Use)
Screenshot (107.53 KB, image/png)
2008-07-22 14:34 UTC, Suzanne Hillman
no flags Details

Description Suzanne Hillman 2008-07-22 14:34:33 UTC
Description of problem:
Firefox about:config 'void warranty' page NEEDS TO GO AWAY; it's not
professional, and it was added relatively recently.

Version-Release number of selected component (if applicable):
firefox-3.0.1-1.el5

How reproducible:
Always

Steps to Reproduce:
1. go to about:config
  
Actual results:
Might void warranty warning (see attached screenshot)

Expected results:
No such warning! If there must be a warning, it should not mention a warranty.

Additional info:
This is not professional, and thus not good for an enterprise product!

Comment 1 Suzanne Hillman 2008-07-22 14:34:33 UTC
Created attachment 312349 [details]
Screenshot

Comment 2 Ben Levenson 2008-07-22 17:57:12 UTC
set 'general.warnOnAboutConfig' to false

Comment 3 RHEL Program Management 2008-07-22 18:01:11 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 11 Martin Stransky 2012-05-04 10:15:32 UTC
We're not going to fix it in RHEL.


Note You need to log in before you can comment on or make changes to this bug.