This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 974
Extension API: chrome.i18n.getMessage #4755
Labels
feature/extensions
fixed-with-brave-core
This issue will automatically resolved with the replacement of Muon with Brave Core.
wontfix
Comments
I'm temporarily working around this issue by providing a stub with the methods I need. The following defines responses for predefined messages, and returns the message key for all other messages. Browser.i18n = chrome.i18n || {
getMessage: function (string) {
switch (string) {
case "@@extension_id":
return "pioclpoplcdbaefihamjohnefbikjilc";
case "@@ui_locale":
return "en-US";
case "@@bidi_dir":
return "ltr";
case "@@bidi_reversed_dir":
return "rtl";
case "@@bidi_start_edge":
return "left"
case "@@bidi_end_edge":
return "right";
default:
return string.toString();
}
}
} |
Related to/duplicate of #4474. |
jonathansampson
changed the title
Evernote: Cannot call chrome.i18n.getMessage (chrome.i18n is undefined)
Extension APIs: chrome.i18n.getMessage
May 10, 2017
Reopening as we are now tracking these issues on a more granular level. |
This was referenced May 10, 2017
Closed
jonathansampson
changed the title
Extension APIs: chrome.i18n.getMessage
Extension API: chrome.i18n.getMessage
Jul 2, 2017
I think it's fair to say we won't be implementing this. We'll get this for free when switching over to Brave Core. Marking as |
bsclifton
added
wontfix
fixed-with-brave-core
This issue will automatically resolved with the replacement of Muon with Brave Core.
labels
Jun 18, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
feature/extensions
fixed-with-brave-core
This issue will automatically resolved with the replacement of Muon with Brave Core.
wontfix
https://developer.chrome.com/extensions/i18n#method-getMessage
Blocks #8327, #6366, #9828
The text was updated successfully, but these errors were encountered: