See: <http://mxr.mozilla.org/mozilla/search?string=GenerateValidFilename> <http://mxr.mozilla.org/mozilla/search?string=validateFileName&tree=mozilla> <http://mxr.mozilla.org/seamonkey/find?string=%2FutilityOverlay.js>

Well, porting bug 223549 would make </toolkit/content/contentAreaUtils.js> "depend" on </browser/base/content/utilityOverlay.js>, which works but doesn't sound good :-/ I think /mail and /suite should use |validateFileName()| from </toolkit/content/contentAreaUtils.js> rather than from their own (copy in) <.../utilityOverlay.js> ! But I don't know how to achieve this (nicely) ? (helpwanted)

(In reply to comment #1) >I think /mail and /suite should use |validateFileName()| from ></toolkit/content/contentAreaUtils.js> rather than from their own (copy in) ><.../utilityOverlay.js> ! >But I don't know how to achieve this (nicely) ? (helpwanted) You would have to look at all the functions in toolkit's contentAreaUtils.js and see if they can safely replace the functions of the same name in mail/suite, so that they can be removed and contentAreaUtils.js loaded instead.

(In reply to comment #2) > You would have to look at all the functions in toolkit's contentAreaUtils.js > and see if they can safely replace the functions of the same name in > mail/suite, so that they can be removed and contentAreaUtils.js loaded instead. Bug 405563 looks like a step toward this ;-> (Yet, it's a kind of catch-22 for now: see bug 409112 for example.) For the current bug, would creating a ("minimal") Toolkit <utilityOverlay.js> make any sense ?

(In reply to comment #3) > Bug 405563 looks like a step toward this ;-> Ah, bug 405653 !

(In reply to comment #3) >For the current bug, would creating a ("minimal") Toolkit <utilityOverlay.js> >make any sense ? I'm not sure what you're suggesting, but it doesn't seem to make sense to me.

(In reply to comment #5) > I'm not sure what you're suggesting, but it doesn't seem to make sense to me. To create a </toolkit/content/utilityOverlay.js> file, with (at least) |GenerateValidFilename()| and |validateFileName()|.

Sorry, but I wouldn't have thought that would be appreciated.