Customize proxy config settings goes into all.js even not selected

VERIFIED WONTFIX

Status

--
minor
VERIFIED WONTFIX
17 years ago
17 years ago

People

(Reporter: jimmyu, Assigned: shrutiv)

Tracking

Details

(Reporter)

Description

17 years ago
In CCK wizard "Customize Proxy Configurations" window, fill in info for Manual 
Proxy Config and Auto Proxy Config URL, but select Direct connection. Build the 
installer and lanuch the browser, go to Edit|Preferences|Advanced|Proxies. And 
see all.js in c:\program files\netscape\netscape 6\defaults\pref that the info 
are present.
(Reporter)

Updated

17 years ago
QA Contact: barrettl → jimmyu
(Assignee)

Comment 1

17 years ago
Does this cause any problem like crash?
(Reporter)

Comment 2

17 years ago
No, this problem doesn't cause any trouble.
(Assignee)

Comment 3

17 years ago
Well, I think we are safe. In the browser, if we fill in info for Manual 
Proxy Config and Auto Proxy Config URL, but select Direct connection and view
pref.js file, we see the info present. CCK also does the same, but CCK writes
info into all.js file. 
Should we mark this bug invalid since it does'nt cause any problem or undesired
behavior?

Comment 4

17 years ago
WONTFIX seems to fit the description better: it is consistent with Browser's
behavior but not necessary correct. Comments?
(Assignee)

Comment 5

17 years ago
Marking WONTFIX.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 6

17 years ago
Personally, I think this is still a bug even though it doesn't causes any
problem. Because a user maybe be modifying a previous config that contains proxy
setting but  decided to use direct connnection for the new config. And those
proxy info exist in the new config. Instead, the user will have to manually
remove the previous proxy info.

This is not a critical problem but I think it will be good for tracking purpose.
Will drop the severity of this bug.
Severity: normal → minor

Comment 7

17 years ago
I think this behavior is OK.  We could add info to the Guide and/or Help, to
clarify this and insruct the users to clear the text fields if they don't want
these values written to the default prefs.

Reopening and assigning to kristif.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---

Comment 8

17 years ago
We could even add text to the screen itself...
Assignee: shrutiv → kristif
Status: REOPENED → NEW

Comment 9

17 years ago
Added a Customizing Proxy Settings section to the CCK 6.2.1 Release Notes with 
this text:

If you customize proxy settings and later edit that configuration to select 
Direct Connection, you need to delete the previous proxy settings in the 
Customize Proxy Configurations window. 


http://Syndicate/docs/client/infodsgn/cck-emojo/relnotes/cck.html

Marking RESOLVED (for CCK 6.2.1) REMIND (for possible fix in future release)
Status: NEW → RESOLVED
Last Resolved: 17 years ago17 years ago
Resolution: --- → REMIND
REMIND is deprecated per bug 35839.
Status: RESOLVED → REOPENED
Resolution: REMIND → ---
->default
Assignee: kristif → shrutiv
Status: REOPENED → NEW
QA Contact: jimmyu → blee
(Assignee)

Comment 12

17 years ago
Marking fixed. This is one of those bugs which was marked REMIND earlier and
automatically changed resloution during bugzilla upgrade.
Status: NEW → RESOLVED
Last Resolved: 17 years ago17 years ago
Resolution: --- → FIXED

Comment 13

17 years ago
This was not FIXED, so it should either be RESOLVED as WONTFIX or INVALID
with an explanation.  Some comments favored WONTFIX and some favored INVALID...
(Assignee)

Comment 14

17 years ago
Reopening. 
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 15

17 years ago
I actually meant to mark it REMIND and accidentally maked fixed. Changing
resolution to WONTFIX, based on comment #4 and #5.
Status: REOPENED → RESOLVED
Last Resolved: 17 years ago17 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 16

17 years ago
mark verified
Status: RESOLVED → VERIFIED
QA Contact: blee → jimmyu
With the 7.0 release, removing information about this bug from the Release Notes 
and adding it to the "Guide to Customizing Netscape 7.0"
You need to log in before you can comment on or make changes to this bug.