…e password input shorter
…n 25% of page width
…lthough in both cases, it should be for a different select altogether, looking into it
…t make sense to temporarily push people to migrate over to :default. Instead, the next release will just have a different (better) implementation of :selected.
…l be gone in 1.0 in favor of after_initialize or controller set-ups
…for example). The dual declarations are required because of our clearfix display hack on the LIs, which is more specific than the more general rule below. Thanks to adurity for testing.
* affecting commit buttons * in 0.9.6 and earlier we called @object.class.human_name, but this resulted in things like "Userpost" instead of "User post" * in 0.9.7 we called @object.class.name.underscore.humanize * 0.9.6 worked for people with their own i18n for model names (human_name falls back to "Userpost" if there's no i18n) * 0.9.7 worked for those without i18n ("User post" instead of "Userpost") * the crappy fallback in human_name is the issue we're routing around (@object.class.name.humanize) * so we now call @object.class.name.underscore.humanize only if it looks like human_name has fallen back to the crappy @object.class.name.humanize
…with the first choice's input, resolving #101.
…ew times, so let's try explicit lines that do what we need to do... specs pass with what I have here, the only real change is we're explicitly requiring Rails 2.3.5 components to explude Rails 3
…er than just formtastic.rb, although it really doesn't matter what it's called" This reverts commit b872f39.
…, better fix is to use Timecop or similar
…avour of a deprecated :selected option (issue #152): * if the object has a value, we should pre-select that at all times, ignoring the :default option * if the object has no value, and :default is provided as a Date/Time then :default should be pre-selected * if the object has no value, and :default is provided as nil then no option should be pre-selected (it will default to the first) * if the object has no value, and :default is not provided then fallback to Time.now (or perhaps a configurable default) * :selected invokes a deprecation warning, but is an alias of :default * it's not a real deprecation, as the behaviour has changed with all the bugs and half-fixes