Determine if removing region.properties from Firefox affects SeaMonkey
Categories
(SeaMonkey :: General, task)
Tracking
(Not tracked)
People
(Reporter: mkaply, Unassigned)
References
(Blocks 1 open bug)
Details
I'm removing region.properties here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1733497
Making a note for the Seamonkey folks in case there is anything that needs to be done.
![]() |
||
Comment 1•1 year ago
•
|
||
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.
Reporter | ||
Comment 2•1 year ago
|
||
Am I missing something? I can't find any protocol handlers in region.properties for Thunderbird or Seamonkey
https://searchfox.org/comm-central/source/mail/locales/en-US/chrome/messenger-region/region.properties
https://searchfox.org/comm-central/source/suite/locales/en-US/chrome/browser/region.properties
https://searchfox.org/comm-central/source/suite/locales/en-US/chrome/mailnews/region.properties
![]() |
||
Comment 3•1 year ago
|
||
I suspect it is the browser.contentHandlers.types. for suite which need to be changed anyway but can't test. I will just tuck the bug to the comm-central meta one. If TB has no problems we should have neitther.
![]() |
||
Comment 4•1 year ago
|
||
Solution in Bug 1750466 should cover suite as a seperate handler file I think.
Reporter | ||
Updated•1 year ago
|
![]() |
||
Comment 5•1 year ago
|
||
Only fixed for Thunderbird:
if (scheme == "mailto" && AppConstants.MOZ_APP_NAME == "thunderbird") {
Description
•