Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tabs have no “down” state #37

Open
alanhogan opened this issue Jul 6, 2011 · 5 comments
Open

Tabs have no “down” state #37

alanhogan opened this issue Jul 6, 2011 · 5 comments

Comments

@alanhogan
Copy link

The button-like tabs seen in the demo do not appear to depress between mousedown and mouseup (the “down” state, :active in CSS). This is different from the buttons (not that the buttons depress well at current; see #36).

@alanhogan
Copy link
Author

Ideally — and you see this a lot in the Mac world, e.g. even in checkboxes — there is not only is the “active” state (current tab, checked checkbox…) distinguished from the inactive (non-current tabs, unchecked checkbox…) state, but both of these states have “down” or depressed states, during the click action. If possible, both active & inactive status should change in similar ways during their respective “down” states. Apple typically darkens UI elements to do this. You can see this with their checkboxes: Checked checkboxes stay blue, but darken a bit. Unchecked ones are still grey, but darken a bit. In Aristo, I think the “reverse gradient” or “lots-o-dark inner shadow” treatments would apply to these tabs (and to the buttons they are based off).

@alanhogan
Copy link
Author

Demo of tabs I made a while back that I thought turned out really well in this regard: http://dl.dropbox.com/u/105727/web/tabs/demo.html

@alanhogan
Copy link
Author

Huh, just noticed the original Aristo theme nails this. They call it the Segmented Control in this demo: http://cappuccino.org/aristo/showcase/

@taitems
Copy link
Owner

taitems commented Jul 11, 2011

Hopefully this will be cleaned up in fixing #36. From the title alone I thought this was related to the regular "tabs" lacking a hit state, which I don't think they ever have. This one should inherit directly from the changes to #36 as I'm pretty sure they use the same classes.

@alanhogan
Copy link
Author

Well, I do think and hoped to argue for what I understand to be jQuery UI “tabs” to have that hit state. Is that not supported in jQuery UI, somehow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants