Changes were introduced in http://hg.mozilla.org/mozilla-central/rev/7521936774c1 This string now needs a new ID. This change has caused warnings on the dashboard (least of the issues), but unless we use a new ID we'll keep using existing outdated strings without the variable in it.
And to further clarify, even the string change alone without the variable would have required a new string ID.
NI to make sure this is visible.
I forgot about this. it sounds like you know what the patch should look like - can you do draft it?
(In reply to Patrick McManus [:mcmanus] from comment #3) > I forgot about this. it sounds like you know what the patch should look like > - can you do draft it? Not really, for once because I currently wouldn't be able to test a patch. Also, it needs to be fixed as soon as possible (before it slips to aurora), and it should be extremely quick for someone familiar with the code.
Created attachment 8755445 [details] [diff] [review] corrupted content string management
Attachment #8755445 - Flags: review?(dd.mozilla)
Attachment #8755445 - Flags: review?(dd.mozilla) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/195c5c59958883a19851ddf5a3016fecf6fb034e Bug 1274729 - corrupted content string management r=dragana
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox49: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
You need to log in before you can comment on or make changes to this bug.