In result of bug 1600528, we now have textActions.ftl. Let's migrate to it all of m-c.

Welp, it actually removes 20 DTD calls from M1!

With this patch, when I enable in FX in a txt field the spell checking I get this error two times:

[Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.readUTF8URI]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: this.L10nRegistry.loadSync :: line 759" data: no] L10nRegistry.jsm:759

With this patch, when I enable in FX in a txt field the spell checking I get this error two times:

Can you provide STR please?

Open https://searchfox.org/ then in one of the two text fields right click and tick Check Spelling on. Now right click again (the Languages menuitem should be shown now) and the errors appear.

Open https://searchfox.org/ then in one of the two text fields right click and tick Check Spelling on. Now right click again (the Languages menuitem should be shown now) and the errors appear.

This is present in central as well and is not specific to this patch.

The source of the exception is that somehow the try/catch here https://searchfox.org/mozilla-central/source/intl/l10n/L10nRegistry.jsm#757-761 doesn't silence the error when we synchronously try to load the FTL file.

It's a red herring - we try to load it from the browser omni.ja first, and then from the toolkit's one where we find it. The first should throw, and it does, it just should be silenced.

You can file it as a new bug.

(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #6)

It's a red herring - we try to load it from the browser omni.ja first, and then from the toolkit's one where we find it. The first should throw, and it does, it just should be silenced.

It's because it's NS_ERROR_FILE_NOT_FOUND instead of the 2 errors that we're specifically looking for.

Filed bug 1605489 for the errors.

Backed out changeset 0267e42c0db5 (bug 1604960) for causing bc permafails

push that caused the backout: https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&selectedJob=282548682&resultStatus=testfailed%2Cbusted%2Cexception%2Cusercancel%2Crunnable&revision=0267e42c0db5cdb265f916deb1824f70cb3bb287&failure_classification_id=2

backout: https://hg.mozilla.org/integration/autoland/rev/ad0df2bff76ff8e9d4fd7eedd7d190628027bbf3

Also this dt:

https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&searchStr=windows%2C10%2Cx64%2Cdebug%2Cmochitests%2Ctest-windows10-64%2Fdebug-mochitest-devtools-chrome-e10s-2%2Cm%28dt2%29&tochange=ad0df2bff76ff8e9d4fd7eedd7d190628027bbf3

Green try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=57fadc384c7d4d54017160b886d2c1c2412a34c6

Minor updates:

• In browser/components/places/content/places.xhtml one MACOS ifdef delete action switched
• devtools/client/webconsole/test/browser/browser_console_context_menu_entries.js updated to new IDs.

Green try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=57fadc384c7d4d54017160b886d2c1c2412a34c6

https://hg.mozilla.org/mozilla-central/rev/ca49196116bb