| Summary | form lowercase data input |
| Queue | Ingo |
| Queue Version | HEAD |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | wolstena (at) sfu (dot) ca |
| Created | 01/09/2005 (7738 days ago) |
| Due | |
| Updated | 01/12/2005 (7735 days ago) |
| Assigned | 01/11/2005 (7736 days ago) |
| Resolved | 01/12/2005 (7735 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
an auto-fill feature. Portions (eg other) of this feature need to be
disabled or the previous value is used. You would think it would let
you re-key a new value.
State ⇒ Not A Bug
browser doing this.
spam. I have selected "any of the following", "X-Spam-Status", "begins
with", "yes". If I try to change "yes" to "Yes", It reverts to "yes"
when I push tab or move to another field with a mouse click. It does
not seem to matter if the case select checkbox is selected or not.
The same problem occurs when creating a new rule.
State ⇒ Assigned
Sieve backend. What rule backend do you use and what are the exact
steps to reproduce this?
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ form lowercase data input
Queue ⇒ Ingo
is converted to lowercase. Hence, it is not possible to do case
sensitive rules.
Sorry, no patch. Me and javascript don't get along.