Closed Bug 149812 Opened 22 years ago Closed 22 years ago
Remove What's Related domain blocking UI
This UI is really geeky and advanced, there's no need for it.
Comment on attachment 86752 [details] [diff] [review] patch Noting r=bryner sr=ben from bugscape bug.
Netscape people can see http://bugscape/show_bug.cgi?id=16256 for more information. Asa has agreed that we can remove the UI for this pref from Mozilla.
qa --> firstname.lastname@example.org
QA Contact: paw → claudius
what are the chances that this will land before 06/12. pls update eta in the status whiteboard. thanks!
Whiteboard: [adt1 RTM] → [adt1 RTM] [ETA Needed]
fixed on trunk.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
claudius - can you pls verify this one on the trunk, so that we can get it checked tomorrow? thanks!
Whiteboard: [adt1 RTM] [ETA Needed] → [adt1 RTM] [06/13]
Comment on attachment 86752 [details] [diff] [review] patch a=scc (on behalf of drivers) for checkin to the mozilla1.0 branch
Attachment #86752 - Flags: approval+
when you check this into the branch, please change the mozilla1.0.1+ keyword to fixed1.0.1
claudius sez VERIFIED FIxed on trunk builds 20020613 on all platforms. marking VERIFIED (for trunk, branch still pending)
Status: RESOLVED → VERIFIED
"This UI is really geeky and advanced, there's no need for it." rofl, is this some kind of joke or something?
Is this gone for good? If so, this bug: http://bugzilla.mozilla.org/show_bug.cgi?id=63909 can go away as well.
As well as: 87082 57431 57564
so it's ok with netscape for mcom domains to leak out? and it's ok with sun for their entire corporate network structure to be passed along to alexa? and it's ok with ibm for their entire corporate network structure to be passed to alexa or some alternative what's related vendor? the first thing i did when i got netscape at a corporation was disable what's related for my corporation's private domains. not doing this would have been negligent.
Whiteboard: [adt1 RTM] [06/18]
The UI is gone, but the pref is still there.
claudius - can pls verify the fix on the 1.0 branch. thanks!
You need to log in before you can comment on or make changes to this bug.