User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 If I create a Message Filter, and enter a name (for the filter), containing Unicode characters, the filter will be created, successfully, HOWEVER, it cannot be futher enabled (clicked, by selecting it's respective checkbox on the the message filter list); fyi, the filter can still be MANUALLY run by hand, on the target specified, by cannot be SELECTED to run automatically. If the filter name, is simply changed to something using only an ASCII charset, the filter is renamed, and can be selected (via the checkbox), without any problem, whatsoever. If the filter is subsequently renamed, to something else containing unicode characters, it will become "unselectable", again. Hence, the bug, is certainly repeatable, and appears to be the result of Unicode, or Non-ASCII Message Filter Names (I would surmise). (FYI: The particular message filter names that I used, contained Japanese characters -- though I assume the issue would persist, regardless of the foreign character set, i.e. Unicode?) Reproducible: Always Steps to Reproduce: 1. Create Message Filter, with name containing Unicode (foreign) characters. 2. Rename Message Filter name, using only ASCII characters. 3. Rename Message Filter, with a name containing Unicode (foreign) characters, again.
have you tried a trunk build? I think jshin fixed a bug like this on the trunk.
(In reply to comment #1) > I think jshin fixed a bug like this on the trunk. i.e. bug 202729 -- if you are using a 1.0.x release of TB, this bug is a dupe and you should resolve it as such.
Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 22.214.171.124)
Whiteboard: closeme 2008-08-28
RESO INCO per lack of response to the last question(s). If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.