Closed Bug 126366 Opened 19 years ago Closed 10 years ago

make Set As Wallpaper support background images

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: hewitt, Assigned: neil)

Details

Just landed support for Set As Wallpaper on images, now I need to make it
support background images, which will be somewhat clumsy since I'll have to use
GetComputedStyle each time the context menu is about to be displayed, and that
might be slow.
Severity: normal → enhancement
Status: NEW → ASSIGNED
Priority: -- → P4
Target Milestone: --- → mozilla1.1
Severity: enhancement → normal
Priority: P4 → --
Target Milestone: mozilla1.1 → ---
We do anyway, for the "show background image" menuitem.
We already have "view background image".  Are you saying we should add "save
background image", "copy background image address", etc?
You can always choose "view background image" then "set as wallpaper". To add the proposed option into the context menu would just clutter it more, no?

Anyway how many people want background images on their desktop? Most background images won't be suitable.
What if "Background Image" was made a menu like Frames have now?  That would get
rid of the clutter.  And give the option to center, stretch, or tile the image
if that is possible.  Tiled would be much more relevant to background images.
"center, stretch, or tile the image" as it is displayed or "center, stretch, or tile the image" and use the manipulated image as the wallpaper?

I'm not sure how useful this would be...
Windows has those options built in.  There is no need for checking or
manipulating anything.  Tiled is particularly useful for background images since
on most webpages, backgrounds are tiled.
Assignee: hewitt → neil.parkwaycc.co.uk
Status: ASSIGNED → NEW
Product: Core → Mozilla Application Suite
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: 10 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.