2

If I am not wrong, __MSG_ placeholders should automatically replaced in manifest and CSS files only, not in HTML files (other files like JS I did not test). In Firefox and Chrome such functionality must be added with own JS, and most developers added some extra functionality which is now broken.

https://developer.chrome.com/docs/extensions/reference/i18n/

Steps to reproduce:
Add "test" in localization file and __MSG_test_ _ (w/o extra space) in any HTML file.

Expected behavior:
__MSG_test_ _ should be not translated.

macOS:
11.6

Image/Video:
<upload images; for videos we recommend using streamable.com>

    Not sure what you mean by this, but can you first check that this is supported in Safari?

      You mean with Safari Extensions? Unfortunately I am not an expert writing Safari extension, too complicated for me, made only (first) one in Chrome and Firefox.

      I know only that __MSG translation placeholders are not replaced in HTML files automatically, only manifest file and CSS as documented in Chrome developer docs.

        Ok so this is related to web extensions.

        Can you give us a step by step instruction to reproduce the issue?

          22 days later
          test.zip
          4kB

          Sorry for delay.

          I wrote an example new tab extension. Please just add it to extensions in Chrome and Orion from disk. Then you should see the following in Chrome:

          1. Extension title MSG_extensionName defined in Manifest is translated in extension overview
          2. After opening a new tab div::after shows translated MSG_cssTest (located in CSS)
          3. But MSG_htmlTest inside the div of HTML file is not translated

          If you open the extension in Orion MSG_htmlTest is translated, which should not. As shown in Chrome docs only MSG placeholders should be translated in Manifest and CSS only. For HTML files developers has care by self.

          Of course maybe its not bad that it works in HTML as well, but I think most Chrome and Firefox extensions have code running which may do more like in my extension and could break the extension. To be backward compatible I would disable it.

            a year later
            No one is typing