Subtle compose

[famanson]

Improvement for Compose box using completely different approach for inputs and textareas

[macduy]

Sean, this is really good, much better! Going forwards, I would like to do this:

Right now the red tooltip saying "0/X chars needed" shows up pretty much straight away when the user clicks on any of the fields. I think this is still too harsh. We should have severity level of errors:

• Errors shown only after the field is "dirty" and are unfocused (e.g. too short)
• Errors shown while typing (e.g. incorrect type, too long) and above

I noticed that Angular marks certain fields ng-dirty when the user has typed in them, so that should help with handling the "dirty" bit.

[famanson]

@macduy heh, the dirty part sounds pretty good, I'll take a look tonight

[famanson]

Errors shown only after the field is "dirty" and are unfocused (e.g. too short)

Are you sure about the unfocused part? If I was told it is too short in the first place, I'd like to see my fix progress on the go. Maybe it should not show the field is too short immediately in first click, but I would rather keep the current behaviour but only allow "too short" to show when it has been dirtied (does that make sense?)

[macduy]

Hmm you are right, we'll need to think about it a bit more. I guess we'd need something like focus-dirty along side dirty to denote whether the user has at least once focused the field.