Closed Bug 110421 Opened 23 years ago Closed 15 years ago

Favicon feature ignores image blocking

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows ME
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: piskozub, Unassigned)

References

(Blocks 1 open bug, )

Details

Attachments

(1 file)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.5+) Gecko/20011114 BuildID: 20011114 Setting a favicon image to an off-site icon makes Mozilla show it even with "Alert me before downloading an image" setting active. I'll attach a testcase soon. This makes it possible to go aroung Mozilla security settings on images. Reproducible: Always Steps to Reproduce: 1. Switch "Alert me before downloading an image" on 2. Check if you have www.playboy.com in your image permissions file. 3. If the permission is "on", delete www.playboy.com entry 4. See the testcase (available also as the URL above)
You need to have favicons (The "Show Web Site Icons" GUI setting) switched on to see the effect. Mozilla never asks about downloading the Playboy icon. Reassigning -> hyatt (the favicon guy)
Assignee: blakeross → hyatt
QA Contact: sairuh → claudius
This should probably be seperate from normal image prefs. When generic content control is implemented this would be handled there, I would think.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Blocks: 120352
Target Milestone: mozilla1.1 → Future
favicons are not standard web page images. A separate preference would be needed. Otherwise, people would consider the missing favicon a glitch.
Product: Core → Mozilla Application Suite
Assignee: hyatt → nobody
Status: ASSIGNED → NEW
QA Contact: claudius → guifeatures
Target Milestone: Future → ---
Component: XP Apps: GUI Features → UI Design
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: