taitems / Aristo-jQuery-UI-Theme

The "Aristo" theme for Cappuccino ported to a jQuery UI Theme

Home Page:http://taitems.github.com/Aristo-jQuery-UI-Theme/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

What happened to active/down state?

alanhogan opened this issue · comments

Looking at http://www.warfuric.com/taitems/demo.html, it seems Aristo included “depressed” / reverse-gradient “down” (:active) states for buttons. Not perfect, but they gave a good pseudo-physical feeling of being activated.

But at what I understand to be an up-to-date, official demo page — http://taitems.github.com/Aristo-jQuery-UI-Theme/ — these are gone! Replaced by a mere change in color.

Frankly, this doesn’t make sense. The buttons are less buttony now. It matches the style of the active tab in Aristo's tabs — but clicking a button (temporary depression) isn’t the same as showing active/selected state. (See also: #37).

I’m curious. What was the thinking behind this change?

I'll look to chuck in an inset box shadow in future, but I'm completely against simply reversing a gradient. The trouble with this approach is that it won't have any effect on IE, so we'll need to account for that.

As to why it was lost from the warfuric hosted version, I rebased the theme to a more recent themeroller output and it simply never made the jump. Some things were bound to slip through the cracks.

Darkening a shade or two is good as well (and cross-browser). (Of course, IE ≤ 8 can do proprietary gradients, and IE9 can do SVG gradient backgrounds.)

Alan Hogan

http://blogic.com
contact@alanhogan.com

On Sunday, July 10, 2011 at 8:50 PM, taitems wrote:

I'll look to chuck in an inset box shadow in future, but I'm completely against simply reversing a gradient. The trouble with this approach is that it won't have any effect on IE, so we'll need to account for that.

As to why it was lost from the warfuric hosted version, I rebased the theme to a more recent themeroller output and it simply never made the jump. Some things were bound to slip through the cracks.

Reply to this email directly or view it on GitHub:
#36 (comment)