Open Bug 627425 Opened 14 years ago Updated 3 years ago

update dialog messages to be from Mozilla Firefox

Categories

(Firefox :: General, defect)

defect

Tracking

()

Future
Tracking Status
blocking2.0 --- -

People

(Reporter: jslater, Unassigned)

Details

Recent research has shown that people tend to view Firefox even more favorably when they understand our mission and non-profit roots. To help encourage that understanding, we're making an effort to reference "Mozilla Firefox" instead of just "Firefox" whenever possible. Naturally, having the product itself reinforce this is the best possible way to make the connection. Can we update the various in-product dialog messages to be from Mozilla Firefox instead of just Firefox?
From an implementation perspective, this *should* be a fairly easy fix, replacing: http://mxr.mozilla.org/mozilla-central/source/other-licenses/branding/firefox/locales/en-US/brand.dtd#1 and http://mxr.mozilla.org/mozilla-central/source/other-licenses/branding/firefox/locales/en-US/brand.properties#1 with "Mozilla Firefox", or replacing the various references to &brandShortName to &brandFullName (though that would have a poor effect on downstream products, I suspect) The QA on this would be pretty intense, though, ensuring that the layout of the various dialogs isn't adversely affected. Also, even though we don't localize the brand name, all locales would have to update their files if we followed option 1. Finally, Limi has expressed some concern over the user experience impact (which I share, fwiw!) All that makes me think this is post Firefox 4 work.
blocking2.0: --- → -
Target Milestone: Firefox 4.0 → Future
(In reply to comment #1) > All that makes me think this is post Firefox 4 work. Yep - I totally understand. Would love to come back to this one for future releases, but certainly don't want to add churn or craziness at this stage.
Short update: working through some potential changes to our brand architecture. I know not much is happening on this bug at the moment anyway, but let's officially put this on pause until a few more things are settled. Should be in the next few weeks, then I'd like to resume the discussion again. Thanks-
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.