Bug 1739814 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Other APIs that are potentially broken from bug 1571672 are listed below. These could cause various breakages with folders that have non-ascii names.

Not all of these are currently used from JavaScript, though some could be used by add-on experiments.

I generated the list by looking through the results of a search for `uri` on `mail**idl`. There may be more under `url`, though mailnews does seem fairly consistent.

* Spam filtering interface: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/search/public/nsIMsgFilterPlugin.idl#56,77,101,138,141,162,186,204,223,253
* Spam folder uris (maybe not, need checking?): https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsISpamSettings.idl#37,46
* nsIMsgMessageService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgMessageService.idl#52,125,197,245
* nsIMsgFolder: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgFolder.idl#521-522,624
* nsIMsgIncomingServer: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgIncomingServer.idl#493
* nsIMsgWindowCommands: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgWindow.idl#21-22
* nsIMsgCompose: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgCompose.idl#242,279
* nsIMsgComposeService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgComposeService.idl#133
* nsIMsgSend: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgSend.idl#323
* nsIPop3Sink: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/local/public/nsIPop3Sink.idl#18-19,22
* nsIPop3URL: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/local/public/nsIPop3URL.idl#12
* nsIMimeStreamConverter: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/mime/public/nsIMimeStreamConverter.idl#91
* nsINntpService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/news/public/nsINntpService.idl#34,36,46
* nsIMsgFilterList: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/search/public/nsIMsgFilterList.idl#85
Revision 1 by
on 
Other APIs that are potentially broken from bug 1571672 are listed below. These could cause various breakages with folders that have non-ascii names.

Not all of these are currently used from JavaScript, though some could be used by add-on experiments.

I generated the list by looking through the results of a search for `uri` on `mail**idl`. There may be more under `url`, though mailnews does seem fairly consistent.

* nsIMsgMessageService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgMessageService.idl#52,125,197,245
* nsIMsgFolder: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgFolder.idl#521-522,624
* nsIMsgIncomingServer: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgIncomingServer.idl#493
* nsIMsgWindowCommands: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgWindow.idl#21-22
* nsIMsgCompose: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgCompose.idl#242,279
* nsIMsgComposeService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgComposeService.idl#133
* nsIMsgSend: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgSend.idl#323
* nsIPop3Sink: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/local/public/nsIPop3Sink.idl#18-19,22
* nsIPop3URL: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/local/public/nsIPop3URL.idl#12
* nsIMimeStreamConverter: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/mime/public/nsIMimeStreamConverter.idl#91
* nsINntpService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/news/public/nsINntpService.idl#34,36,46
* nsIMsgFilterList: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/search/public/nsIMsgFilterList.idl#85
Revision 2 by
on 
Other APIs that are potentially broken from bug 1571672 are listed below. These could cause various breakages with folders that have non-ascii names.

Not all of these are currently used from JavaScript, though some could be used by add-on experiments.

I generated the list by looking through the results of a search for `uri` on `mail**idl`. There may be more under `url`, though mailnews does seem fairly consistent.

* nsIMsgMessageService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgMessageService.idl#52,125,197,245
* nsIMsgFolder: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgFolder.idl#521-522,624
* nsIMsgIncomingServer: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgIncomingServer.idl#493
* nsIMsgWindowCommands: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/base/public/nsIMsgWindow.idl#21-22
* nsIMsgCompose: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgCompose.idl#242,279
* nsIMsgComposeService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgComposeService.idl#133
* nsIMsgSend: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/compose/public/nsIMsgSend.idl#323
* nsIPop3Sink: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/local/public/nsIPop3Sink.idl#18-19,22
* nsIPop3URL: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/local/public/nsIPop3URL.idl#12
* nsIMimeStreamConverter: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/mime/public/nsIMimeStreamConverter.idl#91
* nsINntpService: https://searchfox.org/comm-central/rev/37baa8dd18341e3dd3083347c3b91292b6cddcc9/mailnews/news/public/nsINntpService.idl#34,36,46

Back to Bug 1739814 Comment 0