We still do catch up and while I can build I can't test comm-central SeaMonkey. But I think this will break SeaMonkey and Thunderbird both. We impement the mailto and irc(s) protocols and have different irc handlers in our region.properties too. With the ur handler not application specific this will no longer be effective. It should be handled similar like the search engines and allow for different comm-central handlers for both suite and thunderbird.
Bug 1750031 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We still do catch up and while I can build I can't test comm-central SeaMonkey. But I think this will break SeaMonkey and Thunderbird both. We impement the mailto and irc(s) protocols and have different irc handlers in our region.properties too. With the ur handler not application specific this will no longer be effective. It should be handled similar like the search engines and allow for different comm-central handlers for both MOZ_SUITE and MOZ_THUNDERBIRD.
We still do catch up and while I can build I can't test comm-central SeaMonkey. But I think this will break SeaMonkey and Thunderbird both. We impement the mailto and irc(s) protocols and have different irc handlers in our region.properties too. With the uri handler not application specific this will no longer be effective. It should be handled similar like the search engines and allow for different comm-central handlers for both MOZ_SUITE and MOZ_THUNDERBIRD.