Closed Bug 97409 Opened 23 years ago Closed 23 years ago

Unblocking Images from Server should be as easy as blocking images from server

Categories

(Core :: Graphics: Image Blocking, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
mozilla0.9.6

People

(Reporter: rodd, Assigned: morse)

Details

(Keywords: polish)

Attachments

(1 file, 1 obsolete file)

I accidentally blocked images from a server recently. Unfortunately unblocking images from the same server isn't as easy. To block them I right clicked and accidently hit Block Images from Server. To unblock them I had to search thru the menus. Eventually I tried preferences, after searching various right click menus with no luck. After searching thru the preferences I found images under security, and finally (after looking once and missing it) the button to open another dialog to control images viewing for particular servers. As you can see, turn off images is infinitely easier than turning them back on. I think that if images are turned of for a server, then option to turn them back on needs to appear in the right click menus (and probably all of them even thou the option to block only appears in right click menus relating to images.)
Yep. Where an image is blocked, the item should change to `Unblock Images From this Server'. --> XP Apps: GUI.
Component: User Interface Design → XP Apps: GUI Features
[Reassigning to component owner]
Assignee: mpt → blakeross
Keywords: polish
OS: Linux → All
QA Contact: zach → sairuh
Hardware: PC → All
QA Contact: sairuh → tpreston
--> morse
Assignee: blakeross → morse
Component: XP Apps: GUI Features → Cookies
QA Contact: tpreston → tever
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.6
cc'ing law and alecf for reviews
Comment on attachment 53714 [details] [diff] [review] Add context menu item for unblocking Very nice refactoring.. just one comment: >+ var permissionmanager = >+ Components.classes["@mozilla.org/permissionmanager;1"] >+ .getService().QueryInterface(Components.interfaces.nsIPermissionManager); Can actually be: >+ var permissionmanager = >+ Components.classes["@mozilla.org/permissionmanager;1"] >+ .getService(Components.interfaces.nsIPermissionManager); (note how the interface was moved into the getService() parameters) There's one other place where this is done, below.. with that cleanup, sr=alecf
Attachment #53714 - Flags: superreview+
Revising patch to factor out the declaration of IMAGEPERMISSION into a common file. Otherwise it was defined twice (in cookieTasksOverlay and cookieContextOverlay) and that was causing a duplicate-definition error at program startup. Also including alecf's suggestion in revised patch. alecf, please re-review. law, please review.
Attachment #53714 - Attachment is obsolete: true
Comment on attachment 53785 [details] [diff] [review] avoid duplicate definition of IMAGEPERMISSION r=law
Attachment #53785 - Flags: review+
Comment on attachment 53785 [details] [diff] [review] avoid duplicate definition of IMAGEPERMISSION thanks for that extra cleanup - it avoids an extra AddRef()/Release() as well sr=alecf
Attachment #53785 - Flags: superreview+
fix checked in
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Component: Cookies → Image Blocking
QA Contact: tever → nobody
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: