325198 - Set as Desktop Background very close to Block Images from ...

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Bhavbhuti Nathwani]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Hi all

This is more like nit-picking but you can end up clicking wrong.

The right-click on the image context menu has Set as Desktop Background and Block Images from <sitename> too close by.

I just happended to click on Block instead of Set as, just once of all these times *vbg*.

Could you kindly put in a seperator between these two, or change the placement.

Regards
Bhavbhuti


Reproducible: Always

Comment 1

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 2

[Bhavbhuti Nathwani]

Still an issue in 3.6.3  Just please put a separator after Set As Desktop Background

Thanks

Comment 3

[Tyler Downer [He/Him]]

Are you meaning the adblock plus context menu entry to block? Firefox doesn't have a context menu entry to block images.

Comment 4

[Bhavbhuti Nathwani]

Block Images From < website name >

Is this not a FF default context menu option?  If not I am sorry to have bothered you on this.  In this case, is it possible to force a separator in case an Add-On is trying to add to the context menu?

Thanks for responding.

Comment 5

[Tyler Downer [He/Him]]

No, it isn't. It must be some addon you have.
As for separators, I'm not sure on those. I would talk to the extension author and see if they are planning on putting one in their own extension to prevent that.

Comment 6

[Bhavbhuti Nathwani]

thanks