Bug 1761367 - Firefox DevTools User Docs mention removed Web Develope…

…r submenu r=jdescottes,fluent-reviewers,flod

Differential Revision: https://phabricator.services.mozilla.com/D157789

browser/locales/en-US/browser/browser.ftl

@@ -500,7 +500,7 @@ sharing-warning-disable-for-session =
 
 ## DevTools F12 popup
 
-enable-devtools-popup-description = To use the F12 shortcut, first open DevTools via the Web Developer menu.
+enable-devtools-popup-description2 = To use the F12 shortcut, first open DevTools via the Browser Tools menu.
 
 ## URL Bar
 

browser/locales/en-US/chrome/browser/browser.properties

@@ -661,7 +661,7 @@ troubleshootModeRestartButton=Restart
 # "true" (spelled and capitalized exactly that way) to show the "Text
 # Encoding" menu in the main Firefox button on Windows. Any other value will
 # hide it. Regardless of the value of this setting, the "Text Encoding"
-# menu will always be accessible via the "Web Developer" menu.
+# menu will always be accessible via the "Browser Tools" menu.
 # This is not a string to translate; it just controls whether the menu shows
 # up in the Firefox button. If users frequently use the "Text Encoding"
 # menu, set this to "true". Otherwise, you can leave it as "false".

devtools/client/framework/browser-toolbox/README.md

@@ -8,7 +8,7 @@ To enable it, you must first flip two preferences in the DevTools Options panel
 - Enable browser chrome and add-on debugging toolboxes
 - Enable remote debugging
 
-You can either start it via a keyboard shortcut (CmdOrCtrl+Alt+Shift+I) or via the Tools > Web Developer > Browser Toolbox menu item.
+You can either start it via a keyboard shortcut (CmdOrCtrl+Alt+Shift+I) or via the Tools > Browser Tools > Browser Toolbox menu item.
 
 When describing the setup used by the Browser Toolbox, we will refer to those two distinct Firefox instances as:
 - the target Firefox: this is the current instance, that we want to debug

devtools/client/framework/enable-devtools-popup.js

@@ -9,7 +9,7 @@
  * never been opened by the user.
  *
  * This popup should be anchored below the main hamburger menu of Firefox,
- * which contains the Web Developer menu.
+ * which contains the Browser Tools menu.
  *
  * This is part of the OFF12 experiment which tries to disable F12 by default to
  * reduce accidental usage of DevTools and increase retention of non DevTools

devtools/client/locales/en-US/accessibility.properties

@@ -3,7 +3,9 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the Accessibility panel
-# which is available from the Web Developer sub-menu -> 'Accessibility'.
+# which is in the Developer Tools, available in the
+# Browser Tools sub-menu -> 'Web Developer Tools'
+#
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.
 # You want to make that choice consistent across the developer tools.

devtools/client/locales/en-US/debugger.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the Debugger
-# which is available from the Web Developer sub-menu -> 'Debugger'.
+# which is available from the Browser Tools sub-menu -> 'Debugger'.
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.
 # You want to make that choice consistent across the developer tools.

devtools/client/locales/en-US/dom.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the DOM panel
-# which is available from the Web Developer sub-menu -> 'DOM'.
+# which is available from the Browser Tools sub-menu -> 'DOM'.
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.
 # You want to make that choice consistent across the developer tools.

devtools/client/locales/en-US/har.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the Network Monitor
-# which is available from the Web Developer sub-menu -> 'Network Monitor'.
+# which is available from the Browser Tools sub-menu -> 'Network Monitor'.
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.
 # You want to make that choice consistent across the developer tools.

devtools/client/locales/en-US/inspector.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the Inspector
-# which is available from the Web Developer sub-menu -> 'Inspect'.
+# which is available from the Browser Tools sub-menu -> 'Inspect'.
 #
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.

devtools/client/locales/en-US/memory.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the Memory Tools
-# which is available from the Web Developer sub-menu -> 'Memory'.
+# which is available from the Browser Tools sub-menu -> 'Memory'.
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.
 # You want to make that choice consistent across the developer tools.

devtools/client/locales/en-US/menus.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE (devtoolsRemoteDebugging.label): This is the label for the menu item
-# in Tools > Web Developer. Clicking on this menu item will open about:debugging which
+# in Tools > Browser Tools. Clicking on this menu item will open about:debugging which
 # acts as a hub for debugging remote devices.
 devtoolsRemoteDebugging.label = Remote Debugging
 devtoolsRemoteDebugging.accesskey = R

devtools/client/locales/en-US/netmonitor.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the Network Monitor
-# which is available from the Web Developer sub-menu -> 'Network Monitor'.
+# which is available from the Browser Tools sub-menu -> 'Network Monitor'.
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.
 # You want to make that choice consistent across the developer tools.

devtools/client/locales/en-US/responsive.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the Responsive Design Mode,
-# available from the Web Developer sub-menu -> 'Responsive Design Mode'.
+# available from the Browser Tools sub-menu -> 'Responsive Design Mode'.
 #
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.

devtools/client/menus.js

@@ -6,7 +6,7 @@
 
 /**
  * This module defines the sorted list of menuitems inserted into the
- * "Web Developer" menu.
+ * "Browser Tools" menu.
  * It also defines the key shortcuts that relates to them.
  *
  * Various fields are necessary for historical compatiblity with XUL/addons:

devtools/client/responsive/manager.js

@@ -78,7 +78,7 @@ class ResponsiveUIManager {
    *        Other options associated with toggling.  Currently includes:
    *        - `trigger`: String denoting the UI entry point, such as:
    *          - `toolbox`:  Toolbox Button
-   *          - `menu`:     Web Developer menu item
+   *          - `menu`:     Browser Tools menu item
    *          - `shortcut`: Keyboard shortcut
    * @return Promise
    *         Resolved when the toggling has completed.  If the UI has opened,
@@ -110,7 +110,7 @@ class ResponsiveUIManager {
    *        Other options associated with opening.  Currently includes:
    *        - `trigger`: String denoting the UI entry point, such as:
    *          - `toolbox`:  Toolbox Button
-   *          - `menu`:     Web Developer menu item
+   *          - `menu`:     Browser Tools menu item
    *          - `shortcut`: Keyboard shortcut
    * @return Promise
    *         Resolved to the ResponsiveUI instance for this tab when opening is
@@ -182,7 +182,7 @@ class ResponsiveUIManager {
    *        Other options associated with closing.  Currently includes:
    *        - `trigger`: String denoting the UI entry point, such as:
    *          - `toolbox`:  Toolbox Button
-   *          - `menu`:     Web Developer menu item
+   *          - `menu`:     Browser Tools menu item
    *          - `shortcut`: Keyboard shortcut
    *        - `reason`: String detailing the specific cause for closing
    * @return Promise

devtools/docs/user/about_colon_debugging/index.rst

@@ -12,7 +12,7 @@ Opening the about:debugging page
 There are two ways to open ``about:debugging``:
 
 - Type ``about:debugging`` in the Firefox URL bar.
-- In the **Tools** > **Web Developer** menu, click **Remote Debugging**.
+- In the **Tools** > **Browser Tools** menu, click **Remote Debugging**.
 
 
 When about:debugging opens, on the left-hand side, you'll see a sidebar with two options and information about your remote debugging setup:

devtools/docs/user/accessibility_inspector/index.rst

@@ -26,7 +26,7 @@ When you first open any of the other Developer Tools, the accessibility features
 The accessibility inspector is automatically enabled when you do one of the following(beforeFirefox 79, it had to be explicitly enabled):
 
 
-- Choose **Accessibility** in the **Tools > Web Developer** menu.
+- Choose **Accessibility** in the **Tools > Browser Tools** menu.
 - Select the **Accessibility** tab in the Developer Tools toolbox.
 - Right-click in the main browser window, and choose **Inspect Accessibility Properties** in the context menu.
 - Right-click an item in the HTML pane of the :doc:`Page Inspector <../page_inspector/index>`, and choose **Show Accessibility Properties** in the context menu.

devtools/docs/user/browser_console/index.rst

@@ -20,7 +20,7 @@ Opening the Browser Console
 
 You can open the Browser Console in one of two ways:
 
-1. from the menu: select "Browser Console" from the Web Developer submenu in the Firefox Menu (or Tools menu if you display the menu bar or are on macOS).
+1. from the menu: select "Browser Console" from the Browser Tools submenu in the Firefox Menu (or Tools menu if you display the menu bar or are on macOS).
 
 2. from the keyboard: press :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`J` (or :kbd:`Cmd` + :kbd:`Shift` + :kbd:`J` on a Mac).
 

devtools/docs/user/debugger-api/tutorial-breakpoint/index.rst

@@ -28,7 +28,7 @@ This tutorial was tested against Firefox 58 Beta and Nightly. It does not work i
 
 |br|
 
-3. Visit the HTML file in your browser, and open the Browser Content Toolbox by opening the Firefox menu, choosing “Web Developer”, and then “Browser Content Toolbox”. If that item doesn’t appear in the “Web Developer” menu, make sure you checked both boxes to enable the Browser Content Toolbox as explained in Step 1.
+3. Visit the HTML file in your browser, and open the Browser Content Toolbox by opening the Firefox menu, choosing “Browser Tools”, and then “Browser Content Toolbox”. If that item doesn’t appear in the “Web Developer” menu, make sure you checked both boxes to enable the Browser Content Toolbox as explained in Step 1.
 
 |br|
 

devtools/docs/user/debugger/how_to/open_the_debugger/index.rst

@@ -4,7 +4,7 @@ Open the debugger
 
 There are three ways to open the debugger:
 
-- Select "Debugger" from the Web Developer submenu in the Firefox Menu (or Tools menu if you display the menu bar or are on Mac OSX)
+- Select the *Debugger* panel in the Web Developer Tools, accessible from the Browser Tools submenu
 
 - Press :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`Z` on Windows and Linux, or :kbd:`Cmd` + :kbd:`Opt` + :kbd:`Z` on macOS (starting in Firefox 71; prior to Firefox 66, the letter in this shortcut was :kbd:`S`).
 

devtools/docs/user/dom_property_viewer/index.rst

@@ -21,7 +21,7 @@ The DOM Property Viewer is not enabled by default. To enable it, open the :ref:`
 Opening the DOM Property Viewer
 *******************************
 
-Once enabled, you can open the DOM Property Viewer by selecting "DOM" from the Web Developer submenu in the Firefox Menu Panel (or Tools menu if you display the menu bar or are on macOS), or by pressing its :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`W` keyboard shortcut.
+Once enabled, you can select the *DOM* panel in the Web Developer Tools, accessible from the Browser Tools submenu
 
 The :doc:`Toolbox <../tools_toolbox/index>` will appear at the bottom of the browser window, with the DOM Property Viewer activated. It's just called "DOM" in the Toolbox.
 

devtools/docs/user/eyedropper/index.rst

@@ -16,7 +16,7 @@ Copying a color to the clipboard
 
 Open the Eyedropper in one of these two ways:
 
-- select "Eyedropper" under the "Web Developer" menu
+- select "Eyedropper" under the "Browser Tools" menu
 - open the :doc:`Page Inspector <../page_inspector/index>` tab and click the eyedropper button in its toolbar
 
 As you move the mouse around the page you'll see the current color value in the Eyedropper change. Clicking copies the current color value to the clipboard.

devtools/docs/user/network_monitor/index.rst

@@ -11,7 +11,7 @@ There are a few different ways to open the Network Monitor:
 
 - Press :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`E` (:kbd:`Cmd` + :kbd:`Opt` + :kbd:`E` on a Mac).
 
-- Select "Network" from the Web Developer menu, (which is a submenu of the Tools menu on OS X and Linux).
+- Select the *Network* panel in the Web Developer Tools, accessible from the Browser Tools submenu
 
 - Click the wrench icon |image1|, which is in the main toolbar or under the Hamburger menu |image2|, then select "Network".
 

devtools/docs/user/page_inspector/how_to/open_the_inspector/index.rst

@@ -4,7 +4,7 @@ Open the Inspector
 
 There are two main ways to open the Inspector:
 
-- Choose *Tools > Web Developer > Inspector* from the Menu Bar or the equivalent :ref:`keyboard shortcut <keyboard-shortcuts-opening-and-closing-tools>`.
+- Select the *Inspector* panel in the Web Developer Tools, accessible from the Browser Tools submenu
 - Right-click an element on a web page and select *Inspect Element*.
 
 

devtools/docs/user/responsive_design_mode/index.rst

@@ -13,7 +13,7 @@ Toggling Responsive Design Mode
 There are three ways to toggle Responsive Design Mode:
 
 
-- From the Firefox menu: Select **Responsive Design Mode** from the **Web Developer** submenu in the Firefox Menu (or **Tools** menu if you display the menu bar or are on macOS).
+- From the Firefox menu: Select **Responsive Design Mode** from the **Browser Tools** submenu in the Firefox Menu (or **Tools** menu if you display the menu bar or are on macOS).
 - From the Developer Tools toolbox: Press the **Responsive Design Mode** button in the :ref:`Toolbox's toolbar <tools-toolbox-toolbar>`
 - From the keyboard: Press :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`M` (or :kbd:`Cmd` + :kbd:`Opt` + :kbd:`M` on macOS).
 

devtools/docs/user/storage_inspector/index.rst

@@ -22,7 +22,7 @@ For the time being, the Storage Inspector only gives you a read-only view of sto
 Opening the Storage Inspector
 *****************************
 
-You can open the Storage Inspector by selecting "Storage Inspector" from the Web Developer submenu in the Firefox Menu Panel (or Tools menu if you display the menu bar or are on macOS), or by pressing its :kbd:`Shift` + :kbd:`F9` keyboard shortcut.
+You can open the Storage Inspector by selecting the *Storage* panel in the Web Developer Tools, accessible from the Browser Tools submenu
 
 The :doc:`Toolbox <../tools_toolbox/index>` will appear at the bottom of the browser window, with the Storage Inspector activated. It's just called "Storage" in the Developer Toolbox.
 

devtools/docs/user/style_editor/index.rst

@@ -15,7 +15,7 @@ The Style Editor enables you to:
   <br/>
   <br/>
 
-To open the Style Editor choose the "Style Editor" option from the "Web Developer" menu (which is a submenu in the "Tools" menu on the Mac). The :doc:`Toolbox <../tools_toolbox/index>` will appear at the bottom of the browser window, with the Style Editor activated:
+To open the Style Editor select the *Style Editor* panel in the Web Developer Tools, accessible from the Browser Tools submenu
 
 .. image:: style-editor.png
   :class: center

devtools/docs/user/web_console/index.rst

@@ -47,8 +47,7 @@ Opening the Web Console
 
 You open the Web Console from a menu or with a keyboard shortcut:
 
-
-- Choose **Web Console** from the **Web Developer** submenu in the **Firefox Menu** (or **Tools** menu if you display the menu bar or are on Mac OS X)
+- Select the *Web Console* panel in the Web Developer Tools, accessible from the Browser Tools submenu
 
 - Press the :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`K` (:kbd:`Cmd` + :kbd:`Opt` + :kbd:`K` on OS X) keyboard shortcut.
 

devtools/shared/locales/en-US/debugger.properties

@@ -3,7 +3,7 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 # LOCALIZATION NOTE These strings are used inside the Debugger
-# which is available from the Web Developer sub-menu -> 'Debugger'.
+# which is available from the Browser Tools sub-menu -> 'Debugger'.
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.
 # You want to make that choice consistent across the developer tools.

devtools/shared/locales/en-US/screenshot.properties

@@ -2,9 +2,9 @@
 # License, v. 2.0. If a copy of the MPL was not distributed with this
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
-# LOCALIZATION NOTE These strings are used inside Web Console commands.
-# The Web Console command line is available from the Web Developer sub-menu
-# -> 'Web Console'.
+# LOCALIZATION NOTE These strings are used inside the Web Console commands
+# which can be executed in the Developer Tools, available in the
+# Browser Tools sub-menu -> 'Web Developer Tools'
 #
 # The correct localization of this file might be to keep it in
 # English, or another language commonly spoken among web developers.

devtools/startup/enableDevToolsPopup.inc.xhtml

@@ -9,6 +9,6 @@
          role="alert"
          noautofocus="true"
          orient="vertical">
-    <description data-l10n-id="enable-devtools-popup-description"></description>
+    <description data-l10n-id="enable-devtools-popup-description2"></description>
   </panel>
 </html:template>

js/src/doc/Debugger/Tutorial-Breakpoint.md

@@ -29,8 +29,8 @@ This tutorial was tested against Firefox 58 Beta and Nightly. It does not work i
     ```
 
 3.  Visit the HTML file in your browser, and open the Browser Content Toolbox by
-    opening the Firefox menu, choosing “Web Developer”, and then “Browser
-    Content Toolbox”. If that item doesn't appear in the “Web Developer” menu,
+    opening the Firefox menu, choosing “Browser Tools”, and then “Browser
+    Content Toolbox”. If that item doesn't appear in the “Browser Tools” menu,
     make sure you checked both boxes to enable the Browser Content Toolbox as
     explained in Step 1.