[wp-hackers] CSS backwards compatibility in Admin
wp-hackers at striderweb.com
Wed Nov 5 21:23:58 GMT 2008
Huh. That's pretty funny actually. I think the change then is that
the distinction between buttons is much more emphasized in 2.7 than
2.6. I never noticed the classes, and going through the large number
of plugins I have installed, it appears that none of the other plugin
authors noticed it either! :)
Am I reading your response right that there is a class simply called
"button"? isn't a "submit" control already just a button? Or are you
referring to a "just plain submit"?
On Nov 5, 2008, at 11:07 AM, Andrew Ozz wrote:
> Actually there are 3 classes for buttons now:
> .button has feint gray gradient (very feint, may need to make it a
> little stronger),
> .button-primary with blue-green gradient meant for emphases, one or
> two per page, usually the "main" button,
> .button-secondary has the same gradient like .button but different
> border/highlighting meant for use in areas with background color.
> All existing .button and .button-secondary from 2.5/2.6 are still
> used at the same places. The new .button-primary can be used to
> emphasis the main action on a page, like the "Publish" button on the
> write page, or to draw attention to certain action.
> Stephen Rider wrote:
>> I've noted that in the Admin for 2.7, the submit buttons on Admin
>> pages now have a class="button-primary" assigned.
>> The visual difference is that with this class, the button is a
>> medium blue color, and without it (presumably for "secondary"
>> buttons) the color is a faded gray.
>> For the sake of both a) cleaner code, and b) backwards
>> compatibility with plugins, shouldn't this be reversed?
>> That is, buttons should be blue by default, and IF there is a
>> class="button-secondary" then it is the faded gray? Surely the
>> secondary buttons are the special case here, as most forms have a
>> single, primary, button.
More information about the wp-hackers