1317038 - Make L10N available in the JSON Viewer

Status: NEW

(DevTools :: JSON Viewer, defect, P3)

Description

[Nicolas Chevobbe [:nchevobbe]]

As jryans states in https://bugzilla.mozilla.org/show_bug.cgi?id=1316225#c7 :

> The main complication here is that the JSON View doesn't have an easy way to request the properties file.  l10n files are packaged as chrome:// in a regular build, so the JSON View can't just request arbitrary l10n files at the moment.
> Here are some approaches that would solve this for real:
> 1. For the JSON View's own l10n file, we load[1] those strings in the chrome module that manages the JSON View and pass it down to the content window, giving it access to the strings.  We could do something similar to make the "raw!" loader plugin work for general l10n files.
> 2. We could convert JSON View to use Webpack, similar to what's in progress for the Inspector in bug 1291049.  This would mean the properties get folded into the Webpack bundle and then can be loaded from there.  (Of course, this is my least favorite idea, but I am probably the only one who feels that way at this point...)
> [1]: http://searchfox.org/mozilla-central/rev/846adaea6ccd1428780ed47d0d94da18478acdbb/devtools/client/jsonview/converter-child.js#140

Comment 1

[Nicolas Chevobbe [:nchevobbe]]

See https://bugzilla.mozilla.org/show_bug.cgi?id=1316225#c17 & https://bugzilla.mozilla.org/show_bug.cgi?id=1316225#c20 for insights from bgrins and jdescottes.