[feature] antibookmarks / site blocking




19 years ago
17 years ago


(Reporter: gwalla, Assigned: norrisboyd)



Firefox Tracking Flags

(Not tracked)




19 years ago
This came up during a discussion on website security on slashdot: "I for one 
would like to see antibookmarks. Control-click on a banner, that server is 
blocked. Surf into a trap website, hit an fkey, add its domain to a killfile." 
(posted by Niko).

The relevant discussion is at

Comment 1

19 years ago
I was reading this thread on slashdot and think this is a good idea. I'll see if 
I can get this in.
Component: Bookmarks → Security
Target Milestone: M16

Comment 2

19 years ago
Reassigning to me.
Assignee: slamm → norris


19 years ago
QA Contact: claudius → dougt
This is just a user interface to an aspect of bug #7380.

Comment 4

19 years ago
I'm not so sure about that. Bug 7380 is prefs on a URL by URL basis. This would 

block specific sites (and possibly domains) altogether. Of course, it's 

conveivable that they could share some implementation details, but they're not 

the same issue.

Bug #7380 discusses turning off auto-loading of images for specific URLs and
domains, which part of this is about.

I'm not sure why you'd want to block domains, but if you do, they are
site-by-site, and just another application of bug #7380.

Comment 6

19 years ago
The discussion on Slashdot that spawned this bug was the latest idiocy from 
DoubleClick (i.e., "Oh, yeah, umm... we lied, we really do track you by personal 
information.")  So, as long as <A 
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=7380">#7380</A> will support 
wildcards of some sort, and one of the prefs in question is "Reject all 
connections" or something like that, that should solve the problem.

(By the way, y'all realize that the practice of submitting feature requests as 
bugs just blurs the line between "bugs" and "features" even further... :) )

Comment 7

19 years ago
I suggest to mark this as a duplicate of bug #7380.  If you read the comments
attached to that bug, you will see a comment from:
  yossioren@proxy.co.il  1999-10-12 02:40
which suggests an easy interface for customizing sites.  This is similar to
the Ctrl-click or Function key suggested here, except that you would have to
select "Prefs / Customize this site".  Some other comments attached to bug
#7380 suggest to use regular expressions and to be able to block whole sites
as well as fine-grained URLs.  If you put the bits and pieces together, you
cover everything that is suggested in this enhancement proposal.

If you want to target banner ads specifically, then you could select the
right-click menu, "View this image" and then select "Customize this site".
Another option would be to add a new entry in the right-click menu.

So I think that it would be better to mark this as a duplicate of #7380
and to transfer all votes there.

Comment 8

19 years ago
Sounds like a good plan to me - I had done a search but 7380 does appear to 
include this one.

*** This bug has been marked as a duplicate of 7380 ***
Last Resolved: 19 years ago
Resolution: --- → DUPLICATE
Bug #7380 is an open ended proposal for preferences which are conditional.  The
prefs listed in there are suggestions, but the summary says "all", ie "all that
make sense".

I'll try and get my 7380 discussion document done soon, and include this.

"Bugs" often refers to both around here, you'll ahve to get used to it.

Votes need to be transferred MANUALLY, you can edit your votes using the My
Votes link in the yellow section at the bottom of this bug page.

Comment 10

19 years ago
I'd assumed that site blocking was no longer part of Bug #7380 because it wasn't
orthogonal to the rest of the prefs (IIRC, matty, you were the one who said
that). Is it still part of that bug?

Comment 11

19 years ago
Bulk moving all Browser Security bugs to new Security: General component.  The 
previous Security component for Browser will be deleted.
Component: Security → Security: General

Comment 12

19 years ago
Verified duplicate.
*** Bug 98834 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.