chrome://weave/locale/ is currently pointed at the root of the l10n tree, I don't think that's intentional, and that's definitely confusing my test in bug 1316187, causing all the string files that are shipped but not associated to an existing string chrome package to be reported in chrome://weave/locale.
Created attachment 8848760 [details] [diff] [review] Patch
Attachment #8848760 - Flags: review?(markh)
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/ef70dcc0b2ec Make chrome://weave/locale/ point to the correct folder, r=markh.
Status: NEW → RESOLVED
Last Resolved: a year ago
status-firefox55: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
You need to log in before you can comment on or make changes to this bug.