Closed
Bug 974015
Opened 10 years ago
Closed 10 years ago
Change: "Firefox online services" to "Firefox cloud services"
Categories
(Firefox for Android Graveyard :: Android Sync, defect, P1)
Tracking
(firefox29 wontfix, firefox30 verified, fennec30+)
VERIFIED
FIXED
Firefox 30
People
(Reporter: elan, Assigned: nalexander)
References
Details
We need to change copy "Firefox online services" to "Firefox cloud services" in Fx29. So far, we think this is only 1 string change as seen in: http://mxr.mozilla.org/mozilla-central/search?string=online%20services
Comment 1•10 years ago
|
||
l10nistas: can we late-l10n this change for 29?
Status: NEW → ASSIGNED
tracking-fennec: --- → 29+
Hardware: ARM → All
Comment 2•10 years ago
|
||
If you're asking, the answer is "no". Kinda comes with the territory. In earnest, does "Firefox X services" come as a product name or just a piece of text? If it was a product name, it should be called out as such, and have a localization policy.
Comment 3•10 years ago
|
||
See related Bug 974133 where I'm trying to figure out a policy for "Firefox Account". This string is currently just a piece of text, not a product name.
Keywords: late-l10n
Comment 4•10 years ago
|
||
needinfo'ing jgruen to muster arguments in case he wants to turn an 'ask' into a 'headsup' :P
Flags: needinfo?(jgruen)
Updated•10 years ago
|
tracking-fennec: 29+ → 30+
status-firefox29:
--- → wontfix
status-firefox30:
--- → affected
Keywords: late-l10n
Version: Firefox 29 → Firefox 30
Comment 5•10 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/f3b4874d8395
Target Milestone: --- → Firefox 30
Comment 6•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f3b4874d8395
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 7•10 years ago
|
||
Verified as fixed in Firefox 30 release. Device: Google Nexus 10 (Android 4.4.2).
Updated•7 years ago
|
Product: Android Background Services → Firefox for Android
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•