Closed Bug 115458 Opened 24 years ago Closed 24 years ago

Handle HTML links that are image blocked

Categories

(Core :: Graphics: Image Blocking, defect)

defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 68403

People

(Reporter: xyzzy, Assigned: morse)

References

()

Details

I hate having to report this, seems like a real fringe case, but anyway... If HTML links refer to an image that is blocked, the link is still functional, and the result of a traversal is to go to the URL, but not display the image. This could potentially be very confusing, and doesn't make a lot of sense. If the image is truly "blocked", why should we permit traversal to it? Rather, it would seem appropriate to give the user some kind of feedback that yes, this is a link, but no, you don't want to follow it. OTOH, the user did click the link, so maybe the image should be displayed despite being blocked? Are there similar situations where theis could be at issue?
Whiteboard: DUPEME
This is a dupe of one of the Common UA problem bugs. However if you want to bring up the 'other hand' case, that should be a separate bug if not already filed. *** This bug has been marked as a duplicate of 68403 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
I am considering reopening this, because bug 68403 really deals with providing indicators after a click. For image blocking, no click is required, the link can be validated before it is clicked, even though the user can toggle its block status while the page is still loaded. I don't really feel that 68403 is a dup, and would prefer to see an alternative means of indicating this status, for example, bug 131273.
Component: Cookies → Image Blocking
QA Contact: tever → nobody
*** Bug 212543 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.