Summary | Disable spell-checking button for empty message |
Queue | IMP |
Queue Version | HEAD |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | selsky (at) columbia (dot) edu |
Created | 04/27/2006 (7090 days ago) |
Due | |
Updated | 11/03/2006 (6900 days ago) |
Assigned | |
Resolved | 11/03/2006 (6900 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
something that really isn't broken in the first place.
the user, but spellcheck would be enabled. It might confuse them why
spellcheck is enabled in this situation, but be disabled in a
situation (truly blank message) that may not be discernable to them.
Adding a bunch of javascript to check for this (it may be trivial in
the text case, but it may require quite a bit more for html mode)
doesn't seem to be worth it IMHO.
smells to me like Windows' "Are you really sure you want to move that
object to the trash?" kind-of questions.
get an empty message. So what? I mean, it doesn't break anything or
doesn't do anything unexpected.
State ⇒ Accepted
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Disable spell-checking button for empty message
Queue ⇒ IMP
State ⇒ New
to a blank area. Should the spell-check button just be disabled until
text is actually entered?