-
Notifications
You must be signed in to change notification settings - Fork 1
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
Consistent form styling regardless of Chosen #24
Comments
I think we want to achieve that consistency by making all our selects chosen. That has to be done on the python form level, but if you could make a note of places where they're wrong, that'd be helpful. On Wed, Jul 23, 2014 at 1:52 PM, Naomi I. Morduch Toubman
|
I'm not sure all selects should be chosen. Sometimes they have three options that all start with different things and the change to the UI is not actually helpful. But you think that the lack of consistency is worse than the UI not actually being helpful? |
IMHO the chosen filter field is always an improvement on the default select field. On Wed, Jul 23, 2014 at 1:58 PM, Naomi I. Morduch Toubman
|
v. humble. |
But I'm not immobile on the issue. On Wed, Jul 23, 2014 at 1:58 PM, Naomi I. Morduch Toubman
|
Just making fun :) |
Some selects should be radio buttons instead of Chosen |
🔘👍⚪️👎 ⚪️👊 On Wed, Jul 23, 2014 at 3:49 PM, Stephen Burrows [email protected]
|
OH YOU'RE RIGHT |
Right now, selects with chosen look like they fit with bootstrap, and without chosen look like they don't fit our design. I want everything to be consistent, and maybe with a default more similar to system defaults. Like, maybe let's make selects have similar awful shading to what we're used to, but at least be the same size as everything else.
Thoughts?
The text was updated successfully, but these errors were encountered: