Make WordPress Core

Opened 14 years ago

Closed 9 years ago

#14979 closed enhancement (wontfix)

custom background view shows cropped image and not original upload

Reported by: obvio's profile obvio Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0.1
Component: Customize Keywords: has-patch needs-testing close
Focuses: Cc:

Description

trying to upload a very tall image to the custom background area (for example 100*1100px width*height) works but the image that is then shown in the view-pane is the cropped/thumbnail version of the upload and not the original image the user added.

it is possible a site would have a repeat-x on a really tall image.

Attachments (5)

custom-background.png (205.3 KB) - added by cdog 12 years ago.
14979.diff (10.9 KB) - added by cdog 12 years ago.
14979.png (151.7 KB) - added by cdog 12 years ago.
14979.1.diff (11.0 KB) - added by cdog 11 years ago.
14979.2.diff (628 bytes) - added by cdog 11 years ago.

Download all attachments as: .zip

Change History (18)

#1 @mbijon
13 years ago

  • Cc mike@… added

#2 @DrewAPicture
12 years ago

  • Component changed from UI to Appearance
  • Keywords needs-patch dev-feedback added
  • Milestone changed from Awaiting Review to 3.6

I can reproduce this on current trunk. For example, this is the preview pane of an image sized 150x1000: http://cl.ly/image/32051X0f020S

@cdog
12 years ago

@cdog
12 years ago

#3 @cdog
12 years ago

  • Cc catalin.dogaru@… added
  • Keywords has-patch needs-testing added; needs-patch removed

Agreed. Even this is the intended behavior I found it confusing. It would be better to display the original image instead of its thumbnail.

Also found that saving a custom background from the theme customizer produces unexpected output on the Custom Background screen.

Steps to reproduce:

  1. Upload a custom background from Appearance > Background and save. Everything looks as expected (attachment:custom-background.png, top).
  2. Open the theme customizer (Appearance > Themes > Customize), edit anything and save.
  3. Return to Appearance > Background. Now the original image is displayed instead of its thumbnail and the preview pane is very tall (attachment:custom-background.png, bottom).

This is caused by the update() callback from WP_Customize_Background_Image_Settings class which removes background_image_thumb theme mod.

attachment:14979.diff uses the original image instead of its thumbnail and sets the height of the preview pane properly when a custom background is set. Also adds control over the background size as shown in attachment:14979.png.

Last edited 12 years ago by cdog (previous) (diff)

#6 @ocean90
11 years ago

  • Keywords 3.7-early added
  • Milestone changed from 3.6 to Future Release

#7 @wonderboymusic
11 years ago

  • Milestone changed from Future Release to 3.7

these are all marked 3.7-early

@cdog
11 years ago

#8 @cdog
11 years ago

attachment:14979.1.diff updates the previous patch against current trunk (revision 25008).

#9 follow-up: @nacin
11 years ago

  • Milestone changed from 3.7 to Future Release
  • Type changed from defect (bug) to enhancement

14979.1.diff is a lot. I'm having trouble figuring out what exactly the bug fix is, because that appears to also be a major enhancement. We need to approach the bug fix separately from the enhancement. The background thumbnail is merely for previewing. If it's causing a problem, we should fix that. I'm not entirely sure where the new settings are coming from. If there's a legitimate explanation, that's fine, but this has been classified as a bug when in reality it needed the review as an enhancement.

This also appears to only be a previewing issue (please correct me if I'm wrong), so I'm feeling pretty good about reclassifying this as an enhancement because that seems to be the focus so far.

#10 in reply to: ↑ 9 @cdog
11 years ago

Saving a custom background from the theme customizer produces unexpected output on the Custom Background screen (please see comment:3). You are right, let's discuss the enhancements later and focus on the bug first.

@cdog
11 years ago

#11 @dreamwhisper
11 years ago

  • Cc dreamwhisper added

#12 @celloexpressions
10 years ago

  • Keywords close added; dev-feedback 3.7-early removed

Now that backgrounds are essentially only manageable in the Customizer, this probably isn't an issue anymore?

#13 @wonderboymusic
9 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

no response since comment:12, which was 8 months ago

Note: See TracTickets for help on using tickets.