For reference, I've run a quick check when I got CCed to the bug (after it landed the first time), and fixed a few potential issues (about 5 locales). The check I've run was looking for '<' where en-US had none, but all the examples here have '<' in English as well. https://transvision.mozfr.org/string/?entity=browser/chrome/browser/browser.dtd:addonPostInstallMessage.label&repo=gecko_strings It was all but clear that this would affect only locales, and not en-US, which seems to be the case here. (In reply to Builderb from comment #14) > The US localized build is working so if anyone has this issue you can temp fix it by downloading https://www.mozilla.org/en-US/firefox/68.0a1/releasenotes/ Sorry, that's not a work-around.
Bug 1548990 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For reference, I've run a quick check when I got CCed to the bug (after it landed the first time), and fixed a few potential issues (about 5 locales). The check I've run was looking for '<' where en-US had none, but all the examples here have '<' in English as well. https://transvision.mozfr.org/string/?entity=browser/chrome/browser/browser.dtd:addonPostInstallMessage.label&repo=gecko_strings It was all but clear that this would affect only locales, and not en-US, which seems to be the case here. (In reply to Builderb from comment #14) > The US localized build is working Sorry, that's not a work-around.
For reference, I've run a quick check when I got CCed to the bug (after it landed the first time), and fixed a few potential issues (about 5 locales). The check I've run was looking for HTML tags where en-US had none, but all the examples here have them in English as well. https://transvision.mozfr.org/string/?entity=browser/chrome/browser/browser.dtd:addonPostInstallMessage.label&repo=gecko_strings It was all but clear that this would affect only locales, and not en-US, which seems to be the case here. (In reply to Builderb from comment #14) > The US localized build is working Sorry, that's not a work-around.