Bug 1714788 - doc: Fix a warning 'Inline interpreted text' r=firefox-source-docs-reviewers,championshuttler DONTBUILD

WARNING: Inline interpreted text or phrase reference start-string without end-string.

Depends on D131090

Differential Revision: https://phabricator.services.mozilla.com/D131091
This commit is contained in:
Sylvestre Ledru 2021-11-16 07:59:47 +00:00
Родитель 2c055de75d
Коммит e747d0c0f5
4 изменённых файлов: 5 добавлений и 5 удалений

Просмотреть файл

@ -86,7 +86,7 @@ This tutorial was tested against Firefox 58 Beta and Nightly. It does not work i
7. Press “Run” in the Scratchpad again. Now, clicking on “Click me!” causes the breakpoint hit to be logged twice—one for each ``Debugger`` instance. 7. Press “Run” in the Scratchpad again. Now, clicking on “Click me!” causes the breakpoint hit to be logged twice—one for each ``Debugger`` instance.
Multiple ``Debugger`` instances can observe the same debuggee. Re-running the code in the Scratchpad creates a fresh ``Debugger`` instance, adds the same web page as its debuggee, and then sets a new breakpoint. When you click on the ``div`` element, both ``Debugger``s breakpoints are hit, and both handlers run. Multiple ``Debugger`` instances can observe the same debuggee. Re-running the code in the Scratchpad creates a fresh ``Debugger`` instance, adds the same web page as its debuggee, and then sets a new breakpoint. When you click on the ``div`` element, both ``Debugger``s breakpoints are hit, and both handlers run.
This shows how any number of ``Debugger``-based tools can observe a single web page simultaneously. In fact, you can use the Browser Content Toolboxs Debugger panel to set its own breakpoint in ``report``, and it will trigger along with the first two. Keep in mind, however, that when multiple Debuggers share a debuggee, the order in which their handlers run is not specified. If more than one tool tries to influence the debuggees behavior, their combined behavior could be unpredictable. This shows how any number of ``Debugger``-based tools can observe a single web page simultaneously. In fact, you can use the Browser Content Toolboxs Debugger panel to set its own breakpoint in ``report``, and it will trigger along with the first two. Keep in mind, however, that when multiple Debuggers share a debuggee, the order in which their handlers run is not specified. If more than one tool tries to influence the debuggees behavior, their combined behavior could be unpredictable.

Просмотреть файл

@ -463,7 +463,7 @@ The ToolDefinition object can contain following properties. Most of them are opt
**Integer, optional.** The position of the tool's tab within the toolbox. **Default:** 99 **Integer, optional.** The position of the tool's tab within the toolbox. **Default:** 99
``visibilityswitch`` ``visibilityswitch``
**String, optional.** A preference name that controls the visibility of the tool. **Default: *``devtools.{id}.enabled`` **String, optional.** A preference name that controls the visibility of the tool. **Default: * ``devtools.{id}.enabled``
``icon`` ``icon``
**String, optional.** An URL for the icon to show in the toolbox tab. If undefined the label should be defined. **String, optional.** An URL for the icon to show in the toolbox tab. If undefined the label should be defined.

Просмотреть файл

@ -61,7 +61,7 @@ Deviations from the Mozilla C++ Coding Style
+--------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------+-----------------+-------------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------+-----------------+-------------------------------------------------------------------------------------+
| Mozilla style | Prevalent WAS style | Deviation scope | Evolution | | Mozilla style | Prevalent WAS style | Deviation scope | Evolution |
+========================================================================================================+============================================================================================+=================+=====================================================================================+ +========================================================================================================+============================================================================================+=================+=====================================================================================+
| `We prefer using "static", instead of anonymous C++ namespaces. | Place all symbols that should have internal linkage in a single anonymous | All files | Unclear. The recommendation in the Mozilla code style says this might change in the | | We prefer using "static", instead of anonymous C++ namespaces. | Place all symbols that should have internal linkage in a single anonymous | All files | Unclear. The recommendation in the Mozilla code style says this might change in the |
| | namespace block at the top of an implementation file, rather than declarating them static. | | future depending on debugger support, so this deviation might become obsolete. | | | namespace block at the top of an implementation file, rather than declarating them static. | | future depending on debugger support, so this deviation might become obsolete. |
| | | | | | | | | |
+--------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------+-----------------+-------------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------+-----------------+-------------------------------------------------------------------------------------+

Просмотреть файл

@ -459,8 +459,8 @@ common encodings are:
used for interchange. used for interchange.
In addition, there exist multiple other (legacy) encodings. The Web-relevant In addition, there exist multiple other (legacy) encodings. The Web-relevant
ones are defined in the `Encoding Standard ones are defined in the `Encoding Standard <https://encoding.spec.whatwg.org/>`_.
<https://encoding.spec.whatwg.org/>`_. Conversions from these encodings to Conversions from these encodings to
UTF-8 and UTF-16 are provided by `mozilla::Encoding UTF-8 and UTF-16 are provided by `mozilla::Encoding
<https://searchfox.org/mozilla-central/source/intl/Encoding.h#109>`_. <https://searchfox.org/mozilla-central/source/intl/Encoding.h#109>`_.
Additonally, on Windows the are some rare cases (e.g. drag&drop) where it's Additonally, on Windows the are some rare cases (e.g. drag&drop) where it's