Changeset 21054 for trunk/wp-includes/class-wp-customize-manager.php

Timestamp:

06/11/2012 09:25:05 PM (13 years ago)

Author:

nacin

Message:

Do not specify background-image: none when a user removes a custom background
on a theme that has a default background image.

The onus is on the theme to omit the default background-image from style.css,
to allow the user to remove the default background image. Or, the theme can
specify a background-image for the body selector, as long as they then zero
it out for body.custom-background, like so:

body {
	background-image: url( ... );
}
body.custom-background {
	background-image: none;
}

This allows the theme to be compatible with the custom background feature
but also gracefully degrade if the background feature is disabled.

This is the same behavior as 3.3; setting a default image has simply been
made more prominent in 3.4. Reverts [21013], also parts of [21001].
see #20448 for change and discussion history.

see #20132, which will now be marked as invalid.

Also, per previous changes in #20448, the custom-background class should not
be shown when only a default color is in use.

fixes #20448.

File:

• trunk/wp-includes/class-wp-customize-manager.php (modified) (1 diff)

trunk/wp-includes/class-wp-customize-manager.php

@@ -338 +338 @@
             'values'  => array(),
             'channel' => esc_js( $_POST['customize_messenger_channel'] ),
-            'backgroundImageHasDefault' => current_theme_supports( 'custom-background', 'default-image' ),
         );