Open Bug 1750031 Opened 1 year ago Updated 1 year ago

Determine if removing region.properties from Firefox affects SeaMonkey

Categories

(SeaMonkey :: General, task)

Tracking

(Not tracked)

REOPENED

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.

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.

Summary: Determine if removing region.properties from Firefox affects Seamonkey → Determine if removing region.properties from Firefox affects SeaMonkey

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.

Solution in Bug 1750466 should cover suite as a seperate handler file I think.

Depends on: 1750466
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME

Only fixed for Thunderbird:
if (scheme == "mailto" && AppConstants.MOZ_APP_NAME == "thunderbird") {

Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
You need to log in before you can comment on or make changes to this bug.