[#1118] form lowercase data input
Summary form lowercase data input
Queue Ingo
Queue Version HEAD
Type Bug
State Not A Bug
Priority 2. Medium
Requester wolstena (at) sfu (dot) ca
Created 2005-01-09 (5215 days ago)
Updated 2005-01-12 (5212 days ago)
Assigned 2005-01-11 (5213 days ago)
Resolved 2005-01-12 (5212 days ago)
Patch No

2005-01-12 20:48:31 wolstena (at) sfu (dot) ca Comment #5 Reply to this comment
Darn, sorry for wasting your time. I discovered that the browser has 
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.
2005-01-12 20:02:39 Jan Schneider Comment #4
State ⇒ Not A Bug
Reply to this comment
There is no javascript that changes input field contents. It's your 
browser doing this.
2005-01-12 19:24:54 wolstena (at) sfu (dot) ca Comment #3 Reply to this comment
I'm using Safari 1.2.4. As an example, I have a rule for filtering 
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.
2005-01-11 18:16:24 Jan Schneider State ⇒ Feedback
2005-01-11 18:15:37 Jan Schneider Comment #2
State ⇒ Assigned
Reply to this comment
I can't reproduce this, mixed case rule values work fine here, using a 
Sieve backend. What rule backend do you use and what are the exact 
steps to reproduce this?
2005-01-09 20:14:39 wolstena (at) sfu (dot) ca Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ form lowercase data input
Queue ⇒ Ingo
Reply to this comment
I think there is a bug in the new rule form. When you enter a string it

is converted to lowercase. Hence, it is not possible to do case

sensitive rules.

Sorry, no patch. Me and javascript don't get along.

Saved Queries