1297733 - devtools html localization: investigate usage of properties & dtds outside of devtools folder

Status: RESOLVED INVALID

(DevTools :: General, defect, P3)

Description

[Julian Descottes [:jdescottes]]

Devtools are using several localization files which are not in the devtools folder: 

- chrome://global/locale/globalKeys.dtd, used in:
  - devtools/client/framework/toolbox.xul
- chrome://global/locale/layout_errors.properties, used in:
  - devtools/client/animationinspector/test/browser_animation_animated_properties_displayed.js
- chrome://global/locale/global.dtd, used in:
  - devtools/client/memory/memory.xhtml
- chrome://pippki/locale/certManager.dtd, used in:
  - used devtools/client/netmonitor/netmonitor.xul
- chrome://global/locale/editMenuOverlay.dtd, used in:
  - devtools/client/framework/toolbox.xul
  - devtools/client/projecteditor/chrome/content/projecteditor.xul
  - devtools/client/scratchpad/scratchpad.xul
  - devtools/client/styleeditor/styleeditor.xul
- chrome://branding/locale/brand.properties, used in: 
  - devtools/client/responsivedesign/resize-commands.js
  - devtools/shared/gcli/commands/addon.js
  - devtools/shared/gcli/commands/listen.js
  - devtools/shared/gcli/commands/restart.js
  - devtools/shared/gcli/commands/screenshot.js
  - devtools/shared/system.js

For each of those files we should decide what to do:
- keep using the original file in chrome, and use a fallback value in content
- keep using the original file in chrome, and package it with webpack
- copy the values to an existing or new devtools file
- find an alternative to stop using the file

Comment 1

[Julian Descottes [:jdescottes]]

None of the localization files mentioned in the summary are used by the inspector, removing this bug from the MVP.

Comment 2

[Julian Descottes [:jdescottes]]

Bug summary is outdated and using devtools in content is no longer something we are trying to achieve.