(This bug imported from BugSplat, Netscape's internal bugsystem. It was known there as bug #333657 http://scopus.netscape.com/bugsplat/show_bug.cgi?id=333657 Imported into Bugzilla on 01/27/99 17:24) Linux RTM. This report came from a newsgroup. The user created a new filter -- one to delete the messages where the subject contained a particular URL, and she cut-n-pasted the URL into the text field when she created it. Unfortunately, she also cut-n-pasted a carriage-return before the URL. The mailrule file was written out with an extra return in the condition field. The next time she tried to edit filters, she got the message "Warning: Null child passed to XtManageChildren," and she couldn't see or get to her filters at all after that. As a workaround, we manually edited her mailrule file, which restored things, but perhaps we should fix this for 4.51. I'm trying not to wonder how many other fields this could affect. Assigned to marek, cc sspitzer, because I don't know how sustaining engineering is staffed or broken down yet.

Will not be fixed in 4.5x. Assiging to daver for consideration in 5.0.

set tfv to 5.0 since this bug will never be fixed in a maintenance release, per marek. Can change tfv to something more granular later on. Also, I'm not sure how we're going to work with bugzilla, but this bug can be moved there later if needed.

Maybe the filter I/O code could fix this by doing some data validation. Reassigning to bienvenu, cc mscott

Setting all current Open/Normal to M4.

qa contact to laurel

God knows who this bug belongs to in the new world order...I was thinking of porting the filter code, but it doesn't belong before dog food, and also requires porting the search code.

M7

> God knows who this bug belongs to in the new world order Didn't you port the filter code? :-) Reassigning to bienvenu, and pushing to M8.

No idea if this bug is still valid, and can't test too well without a UI - moving off to m12, especially since there's no xfe anymore.

We'd want to test this on all platforms when implemented so changing to ALL.

I don't think this needs to be fixed before PR1

(target milestone is M11 or M12 - add to beta tracking bug)

We don't even know if this bugs exists in 5.0, since we have no UI. Moving to m20.

laurel - can you try this in the new filter UI and process accordingly?

marking worksforme - Laurel, do you want to try it?

OK using jul6 commercial build linux rh6.0