From 9d7d4a88d60ed326f35881b43e6a2c3e3c633df6 Mon Sep 17 00:00:00 2001 From: Jean-Yves Perrier Date: Thu, 15 Jul 2021 15:19:19 +0200 Subject: [PATCH] Fix Console -> console --- .../first_steps/a_first_splash/index.html | 2 +- .../javascript/first_steps/arrays/index.html | 2 +- .../first_steps/what_went_wrong/index.html | 2 +- .../vue_methods_events_models/index.html | 2 +- .../javascript/index.html | 2 +- .../introducing_complete_toolchain/index.html | 2 +- .../api/proxy/register/index.html | 2 +- .../debugging_(before_firefox_50)/index.html | 2 +- .../mozilla/firefox/releases/29/index.html | 2 +- .../mozilla/firefox/releases/30/index.html | 4 +-- .../mozilla/firefox/releases/34/index.html | 2 +- .../mozilla/firefox/releases/37/index.html | 2 +- .../mozilla/firefox/releases/40/index.html | 2 +- .../mozilla/firefox/releases/6/index.html | 2 +- .../mozilla/firefox/releases/62/index.html | 4 +-- files/en-us/tools/browser_console/index.html | 4 +-- .../tools/debugger/set_a_logpoint/index.html | 2 +- .../tools/migrating_from_firebug/index.html | 4 +-- .../en-us/tools/performance/how_to/index.html | 2 +- .../tools/performance/waterfall/index.html | 6 ++-- .../web_console/console_messages/index.html | 32 +++++++++---------- .../tools/web_console/helpers/index.html | 4 +-- .../tools/web_console/remoting/index.html | 2 +- .../api/workerglobalscope/console/index.html | 2 +- .../global_objects/array/foreach/index.html | 2 +- 25 files changed, 47 insertions(+), 47 deletions(-) diff --git a/files/en-us/learn/javascript/first_steps/a_first_splash/index.html b/files/en-us/learn/javascript/first_steps/a_first_splash/index.html index 36d0f57102b2df9..a5c17fd6b7e4a52 100644 --- a/files/en-us/learn/javascript/first_steps/a_first_splash/index.html +++ b/files/en-us/learn/javascript/first_steps/a_first_splash/index.html @@ -531,7 +531,7 @@

Loops

  1. A starting value: In this case we are starting a count at 1, but this could be any number you like. You could replace the letter i with any name you like too, but i is used as a convention because it's short and easy to remember.
  2. A condition: Here we have specified i < 21 — the loop will keep going until i is no longer less than 21. When i reaches 21, the loop will no longer run.
    3. -
  3. An incrementor: We have specified i++, which means "add 1 to i". The loop will run once for every value of i, until i reaches a value of 21 (as discussed above). In this case, we are printing the value of i out to the console on every iteration using {{domxref("Console.log", "console.log()")}}.
    4. +
  4. An incrementor: We have specified i++, which means "add 1 to i". The loop will run once for every value of i, until i reaches a value of 21 (as discussed above). In this case, we are printing the value of i out to the console on every iteration using {{domxref("console.log", "console.log()")}}.

Now let's look at the loop in our number guessing game — the following can be found inside the resetGame() function:

diff --git a/files/en-us/learn/javascript/first_steps/arrays/index.html b/files/en-us/learn/javascript/first_steps/arrays/index.html index 0208f647fcb8eda..f11c720d290d4c4 100644 --- a/files/en-us/learn/javascript/first_steps/arrays/index.html +++ b/files/en-us/learn/javascript/first_steps/arrays/index.html @@ -100,7 +100,7 @@

Finding the length of an array

  1. Start looping at item number 0 in the array.
  2. Stop looping at the item number equal to the length of the array. This works for an array of any length, but in this case it stops looping at item number 7 (this is good, as the last item — which we want the loop to include — is item 6).
    3. -
  3. For each item, print it out to the browser console with console.log().
    4. +
  4. For each item, print it out to the browser console with console.log().

Some useful array methods

diff --git a/files/en-us/learn/javascript/first_steps/what_went_wrong/index.html b/files/en-us/learn/javascript/first_steps/what_went_wrong/index.html index 7a4a97d868ba578..bc32e3a713b3d73 100644 --- a/files/en-us/learn/javascript/first_steps/what_went_wrong/index.html +++ b/files/en-us/learn/javascript/first_steps/what_went_wrong/index.html @@ -105,7 +105,7 @@

Syntax errors round two

console.log(lowOrHi);
-

Note: console.log() is a really useful debugging function that prints a value to the console. So it will print the value of lowOrHi to the console as soon as we have tried to set it in line 48.

+

Note: console.log() is a really useful debugging function that prints a value to the console. So it will print the value of lowOrHi to the console as soon as we have tried to set it in line 48.

  • Save and refresh, and you should now see the console.log() result in your console. Sure enough, lowOrHi's value is null at this point, so there is definitely a problem with line 48.
    • diff --git a/files/en-us/learn/tools_and_testing/client-side_javascript_frameworks/vue_methods_events_models/index.html b/files/en-us/learn/tools_and_testing/client-side_javascript_frameworks/vue_methods_events_models/index.html index c7c93c5b1ecdd56..fadc318e302bc9a 100644 --- a/files/en-us/learn/tools_and_testing/client-side_javascript_frameworks/vue_methods_events_models/index.html +++ b/files/en-us/learn/tools_and_testing/client-side_javascript_frameworks/vue_methods_events_models/index.html @@ -162,7 +162,7 @@

    Creating a method &a -

    If you try submitting the form now, you'll notice that the page doesn't reload. If you open the console, you can see the results of the console.log() we added inside our onSubmit() method.

    +

    If you try submitting the form now, you'll notice that the page doesn't reload. If you open the console, you can see the results of the console.log() we added inside our onSubmit() method.

    Binding data to inputs with v-model

    diff --git a/files/en-us/learn/tools_and_testing/cross_browser_testing/javascript/index.html b/files/en-us/learn/tools_and_testing/cross_browser_testing/javascript/index.html index ee695eef3183a48..a5f2ed54fc80cd7 100644 --- a/files/en-us/learn/tools_and_testing/cross_browser_testing/javascript/index.html +++ b/files/en-us/learn/tools_and_testing/cross_browser_testing/javascript/index.html @@ -144,7 +144,7 @@

    Browser developer tools

    The Console API

    -

    You may already know what is wrong with this code, but let's explore it some more to show how you could investigate this. For a start, there is a Console API that allows JavaScript code to interact with the browser's JavaScript console. It has a number of features available, but the main one you'll use often is console.log(), which prints a custom message to the console.

    +

    You may already know what is wrong with this code, but let's explore it some more to show how you could investigate this. For a start, there is a Console API that allows JavaScript code to interact with the browser's JavaScript console. It has a number of features available, but the main one you'll use often is console.log(), which prints a custom message to the console.

    Try inserting the following line just below line 31 (bolded above):

    diff --git a/files/en-us/learn/tools_and_testing/understanding_client-side_tools/introducing_complete_toolchain/index.html b/files/en-us/learn/tools_and_testing/understanding_client-side_tools/introducing_complete_toolchain/index.html index 3be17dadf7e799e..1ffabf9cd9eff4f 100644 --- a/files/en-us/learn/tools_and_testing/understanding_client-side_tools/introducing_complete_toolchain/index.html +++ b/files/en-us/learn/tools_and_testing/understanding_client-side_tools/introducing_complete_toolchain/index.html @@ -332,7 +332,7 @@

    Configuring our tools

    } } -

    The above eslint configuration says that we want to use the "recommended" eslint settings, that we're going to allow usage of ES6 features (such as map() or Set()), that we can use module import statements, and that using console.log() is allowed.

    +

    The above eslint configuration says that we want to use the "recommended" eslint settings, that we're going to allow usage of ES6 features (such as map() or Set()), that we can use module import statements, and that using console.log() is allowed.

  • However, in the project's source files we are using React JSX syntax (for your real projects you might use React or Vue or any other framework, or no framework at all!).

    diff --git a/files/en-us/mozilla/add-ons/webextensions/api/proxy/register/index.html b/files/en-us/mozilla/add-ons/webextensions/api/proxy/register/index.html index 87c99d7901267e4..3905167d3752918 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/proxy/register/index.html +++ b/files/en-us/mozilla/add-ons/webextensions/api/proxy/register/index.html @@ -107,7 +107,7 @@

    PAC file environment

    //  pac.js
diff --git a/files/en-us/mozilla/add-ons/webextensions/debugging_(before_firefox_50)/index.html b/files/en-us/mozilla/add-ons/webextensions/debugging_(before_firefox_50)/index.html
index 9820ab84d0243bf..ebcfb413d1e0ed9 100644
--- a/files/en-us/mozilla/add-ons/webextensions/debugging_(before_firefox_50)/index.html
+++ b/files/en-us/mozilla/add-ons/webextensions/debugging_(before_firefox_50)/index.html
@@ -133,7 +133,7 @@ 
    Viewing log output
    
  
  • content scripts.
    • 
 
 
-
    It includes messages your code logs using the Console API as well as any error messages logged by the JavaScript engine as it executes your code.
    
+
    It includes messages your code logs using the Console API as well as any error messages logged by the JavaScript engine as it executes your code.
    
 
 
    Let's try it with the example above: select the Console tab in the Browser Toolbox, open a web page, and click a link to see messages logged from the content script and the background script:
    
 
diff --git a/files/en-us/mozilla/firefox/releases/29/index.html b/files/en-us/mozilla/firefox/releases/29/index.html
index 5d89fbf0f9f8672..8a307a0c767264d 100644
--- a/files/en-us/mozilla/firefox/releases/29/index.html
+++ b/files/en-us/mozilla/firefox/releases/29/index.html
@@ -15,7 +15,7 @@ 
    Developer Tools
    
 
 
      
  
    • Vastly improved web console - Arrays are shown inline without clicking to bring up in the right inspector, window objects show their url, etc.
      • 
- 
    • Added the console API to Web Workers (bug 620935). Now you can log messages to the Web Console from Web Workers.
      • 
+ 
    • Added the console API to Web Workers (bug 620935). Now you can log messages to the Web Console from Web Workers.
      • 
  
    • The Network Monitor tool now shows performance statistics using pie charts ({{bug(846601)}}).
      • 
  
    • On the Inspector, preview tooltips of CSS transforms are now available ({{bug(726427)}}).
      • 
  
    • DOM elements seen in the debugger and console can be removed or inspected directly, via the new buttons to the right of the variable listing.
      • 
diff --git a/files/en-us/mozilla/firefox/releases/30/index.html b/files/en-us/mozilla/firefox/releases/30/index.html
index e4a78c3c0a5e201..869a7cbb9915671 100644
--- a/files/en-us/mozilla/firefox/releases/30/index.html
+++ b/files/en-us/mozilla/firefox/releases/30/index.html
@@ -12,7 +12,7 @@ 
      Developer Tools
      
 
        
  
      • A Box Model Highlighter has been implemented ({{bug(663778)}}).
        • 
  
      • Anywhere a DOM node appears in the console output, it is highlighted when you hover over that console output ({{bug(757866)}}). Similarly all JS functions and objects are highlighted in the console output ({{bug(584733)}}). More information about the console improvement can be found in this blog post.
        • 
- 
      • Support for {{domxref("Console.count()")}} has been added ({{bug(922208)}}).
        • 
+ 
      • Support for {{domxref("console.count()")}} has been added ({{bug(922208)}}).
        • 
 
      
 
 
      CSS
      
@@ -53,7 +53,7 @@ 
      Interfaces/APIs/DOM
      
  
    • The non-standard {{domxref("ArchiveReader")}} and {{domxref("ArchiveRequest")}} are no longer exposed to the Web ({{bug(968883)}}).
      • 
  
    • WebIDL constructors cannot be called as functions anymore. They need to be preceded by the keyword new. ({{bug(916644)}})
      • 
  
    • Added support for a new value (alpha) for the second, optional, parameter of the {{domxref("HTMLCanvasElement.getContext()")}} method allowing to define if alpha blending must be stored or not for this context. When not, the per-pixel alpha value in this store is always 1.0. This allows the back-end to implement a fast-track. ({{bug(982480)}})
      • 
- 
    • {{domxref("GlobalWorkerScope.console")}} now returns for the regular {{domxref("Console")}}; WorkerConsole has been removed ({{bug(965860)}}).
      • 
+ 
    • {{domxref("GlobalWorkerScope.console")}} now returns for the regular {{domxref("console")}}; WorkerConsole has been removed ({{bug(965860)}}).
      • 
  
    • The {{domxref("WebGL_debug_shaders")}} WebGL extension has been implemented ({{bug(968374)}}).
      • 
 
    
 
diff --git a/files/en-us/mozilla/firefox/releases/34/index.html b/files/en-us/mozilla/firefox/releases/34/index.html
index cfc437e4aec2385..d4aed21a9059c92 100644
--- a/files/en-us/mozilla/firefox/releases/34/index.html
+++ b/files/en-us/mozilla/firefox/releases/34/index.html
@@ -19,7 +19,7 @@ 
    Developer Tools
    
  
  • Storage Inspector: a new tool enabling you to view data stored by web pages
    • 
  
  • Performance tool: revamped Profiler UI and frame rate timeline
    • 
  
  • Frame switching: point the developer tools at a specific iframe in the page
    • 
- 
  • console.table support
    • 
+ 
  • console.table support
    • 
  
  • jQuery events are visible in the Page Inspector
    • 
 
 
diff --git a/files/en-us/mozilla/firefox/releases/37/index.html b/files/en-us/mozilla/firefox/releases/37/index.html
index eb08cee449a12b7..7ba2ab85500a7da 100644
--- a/files/en-us/mozilla/firefox/releases/37/index.html
+++ b/files/en-us/mozilla/firefox/releases/37/index.html
@@ -77,7 +77,7 @@ 
    Interfaces/APIs/DOM
  • In keeping with the evolving WebRTC specification, we have deprecated {{domxref("RTCIceServer.url")}} in favor of {{domxref("RTCIceServer.urls")}}, which lets you specify more than one URL for a given ICE server.
  • Some key names of KeyboardEvent.key are changed for conforming the latest DOM Level 3 Events spec. See the tables of KeyboardEvent.key values in MDN. The green cells are new values. And purple values are still unstable. Be careful if you use them (meta bug for these changes is {{bug(900372)}}).
    • -
  • The {{domxref("Console")}} interface is now working on {{domxref("ServiceWorker")}} and {{domxref("SharedWorker")}}. It was previously available but not working ({{bug(1058644)}}).
    • +
  • The {{domxref("console")}} interface is now working on {{domxref("ServiceWorker")}} and {{domxref("SharedWorker")}}. It was previously available but not working ({{bug(1058644)}}).
  • The value of {{domxref("KeyboardEvent.key")}} was incorrectly being reported as "RomanCharacters" when the 英数 (Eisu) key was pressed. Now it correctly returns "Eisu".
    • diff --git a/files/en-us/mozilla/firefox/releases/40/index.html b/files/en-us/mozilla/firefox/releases/40/index.html index 26a729c141c327e..8c8f97ab81013bd 100644 --- a/files/en-us/mozilla/firefox/releases/40/index.html +++ b/files/en-us/mozilla/firefox/releases/40/index.html @@ -141,7 +141,7 @@

    IndexedDB

    Dev Tools

    MathML

    diff --git a/files/en-us/mozilla/firefox/releases/6/index.html b/files/en-us/mozilla/firefox/releases/6/index.html index 06f42cdb7203cdc..6321470281d8178 100644 --- a/files/en-us/mozilla/firefox/releases/6/index.html +++ b/files/en-us/mozilla/firefox/releases/6/index.html @@ -134,7 +134,7 @@

    Other changes

  • Support for microsummaries has been removed; these were never widely used, were not very discoverable, and continuing to support them was making improvements to the Places (bookmark and history) architecture difficult.
  • WebGL now supports the OES_texture_float extension.
  • The new Scratchpad tool provides a handy place to experiment with JavaScript code.
    • -
  • The console.trace() method has been added to the ConsoleAPI (see {{ bug('585956') }}).
    • +
  • The console.trace() method has been added to the Console API (see {{ bug('585956') }}).

    • Changes for Mozilla and add-on developers

    diff --git a/files/en-us/mozilla/firefox/releases/62/index.html b/files/en-us/mozilla/firefox/releases/62/index.html index c35030c20c9e920..ed8273359483166 100644 --- a/files/en-us/mozilla/firefox/releases/62/index.html +++ b/files/en-us/mozilla/firefox/releases/62/index.html @@ -93,8 +93,8 @@

    DOM

  • The {{domxref("Navigator.registerContentHandler()")}} method has been disabled by default in preparation for being removed entirely, as it's been obsolete for some time ({{bug(1460481)}}).
  • The {{domxref("DataTransfer.DataTransfer", "DataTransfer()")}} constructor has been implemented ({{bug(1351193)}}).
  • {{domxref("Document.domain")}} can no longer return null ({{bug(819475)}}). If the domain cannot be identified, then domain returns an empty string instead of null.
    • -
  • Added the {{domxref("Console.timeLog()")}} method to display the current value of a console timer while continuing to track the time ({{bug(1458466)}}).
    • -
  • Added {{domxref("Console.countReset()")}} to reset a console counter value ({{bug(1459279)}}).
    • +
  • Added the {{domxref("console.timeLog()")}} method to display the current value of a console timer while continuing to track the time ({{bug(1458466)}}).
    • +
  • Added {{domxref("console.countReset()")}} to reset a console counter value ({{bug(1459279)}}).

    • DOM events

    diff --git a/files/en-us/tools/browser_console/index.html b/files/en-us/tools/browser_console/index.html index f3ccc2286de004f..820c56cc966e734 100644 --- a/files/en-us/tools/browser_console/index.html +++ b/files/en-us/tools/browser_console/index.html @@ -57,7 +57,7 @@

    Browser Console logging

    @@ -85,7 +85,7 @@

    Console.jsm

    Learn more:

    diff --git a/files/en-us/tools/debugger/set_a_logpoint/index.html b/files/en-us/tools/debugger/set_a_logpoint/index.html index 134402ab6a7e3c4..1b21dac60b52806 100644 --- a/files/en-us/tools/debugger/set_a_logpoint/index.html +++ b/files/en-us/tools/debugger/set_a_logpoint/index.html @@ -12,7 +12,7 @@ ---

    {{ToolsSidebar}}

    -

    Sometimes you want to view a value in your code but you don't want to pause execution. Rather than sprinkle console.log() statements throughout your code, you can use a special type of breakpoint, the logpoint. Logpoints print a message to the Console panel instead of pausing code execution.

    +

    Sometimes you want to view a value in your code but you don't want to pause execution. Rather than sprinkle console.log() statements throughout your code, you can use a special type of breakpoint, the logpoint. Logpoints print a message to the Console panel instead of pausing code execution.

    The logpoint is especially useful in cases where breaking the execution breaks testing procedures, such as when you are debugging popup windows, or executing focus-related logic.

    diff --git a/files/en-us/tools/migrating_from_firebug/index.html b/files/en-us/tools/migrating_from_firebug/index.html index d108946b62dc4ba..cca52766bb66ed0 100644 --- a/files/en-us/tools/migrating_from_firebug/index.html +++ b/files/en-us/tools/migrating_from_firebug/index.html @@ -49,7 +49,7 @@

    Command Line API

    Console API

    -

    To log things to the console from within the web page Firebug makes a Console API available within the page. The Developer Tools share the same API, so your console.* statements will continue to work.

    +

    To log things to the console from within the web page Firebug makes a Console API available within the page. The Developer Tools share the same API, so your console.* statements will continue to work.

    Persist logs

    @@ -193,7 +193,7 @@

    Searching within the style sheets

    Performance Tool -

    Firebug allows to profile JavaScript performance via the "Profile" button within the Console panel or the console.profile() and console.profileEnd() commands. The DevTools provide advanced tooling regarding performance profiling. A profile can be created via console.profile() and console.profileEnd() like in Firebug or via the "Start Recording Performance" button in the Performance Tool. The output of the Call Tree is the one that comes nearest to the output in Firebug, but the Performance panel provides much more information than just the JavaScript performance. E.g. it also provides information about HTML parsing or layout.

    +

    Firebug allows to profile JavaScript performance via the "Profile" button within the Console panel or the console.profile() and console.profileEnd() commands. The DevTools provide advanced tooling regarding performance profiling. A profile can be created via console.profile() and console.profileEnd() like in Firebug or via the "Start Recording Performance" button in the Performance Tool. The output of the Call Tree is the one that comes nearest to the output in Firebug, but the Performance panel provides much more information than just the JavaScript performance. E.g. it also provides information about HTML parsing or layout.

    This is the part where Firebug and the DevTools differ the most, because the outputs are completely different. While Firebug focuses on JavaScript performance and provides detailed information about JavaScript function calls during the profiling session, the Performance Tool in the DevTools offers a broad spectrum of information regarding a website's performance but doesn't go into detail regarding JavaScript function calls.

    diff --git a/files/en-us/tools/performance/how_to/index.html b/files/en-us/tools/performance/how_to/index.html index edbd14199de9697..9e6ceaf952eee22 100644 --- a/files/en-us/tools/performance/how_to/index.html +++ b/files/en-us/tools/performance/how_to/index.html @@ -18,7 +18,7 @@

    Record a profile

    -

    You can also start and stop recording from the Web Console, using console.profile() and console.profileEnd().

    +

    You can also start and stop recording from the Web Console, using console.profile() and console.profileEnd().

    Save a profile

    diff --git a/files/en-us/tools/performance/waterfall/index.html b/files/en-us/tools/performance/waterfall/index.html index 63d5128d765c89f..6e364b5ce5ba91c 100644 --- a/files/en-us/tools/performance/waterfall/index.html +++ b/files/en-us/tools/performance/waterfall/index.html @@ -214,7 +214,7 @@

    Markers

    Timestamp

    -

    A single call to console.timeStamp().

    +

    A single call to console.timeStamp().

    @@ -358,7 +358,7 @@

    Garbage collection

    Adding markers with the console API

    -

    Two markers are directly controlled by console API calls: "Console" and "Timestamp".

    +

    Two markers are directly controlled by console API calls: "Console" and "Timestamp".

    Console markers

    @@ -437,7 +437,7 @@

    Timestamp markers

    Timestamps enable you to mark an instant in the recording.

    -

    To make a timestamp marker, call console.timeStamp(). You can pass an argument to label the timestamp.

    +

    To make a timestamp marker, call console.timeStamp(). You can pass an argument to label the timestamp.

    For example, suppose we adapt the code above to make a timestamp every 10 iterations of the loop, labeled with the iteration number:

    diff --git a/files/en-us/tools/web_console/console_messages/index.html b/files/en-us/tools/web_console/console_messages/index.html index f7a5e529db56069..b68b1910e89a3f1 100644 --- a/files/en-us/tools/web_console/console_messages/index.html +++ b/files/en-us/tools/web_console/console_messages/index.html @@ -133,7 +133,7 @@

    Source maps

    Async stack frames

    -

    Stack traces show stack frames for async functions separately from those for synchronous functions. When you run code containing an async function, its traces (console.trace or thrown error) are shown with an Async: prefix.

    +

    Stack traces show stack frames for async functions separately from those for synchronous functions. When you run code containing an async function, its traces (console.trace or thrown error) are shown with an Async: prefix.

    Console log showing a trace containing async code

    @@ -222,27 +222,27 @@

    Logging

    Messages logged from Shared Workers, Service Workers, add-ons, and Chrome Workers are not shown by default. Use the filtering feature to show them.

    -

    The Logging category includes messages logged using the Console API.

    +

    The Logging category includes messages logged using the Console API.

    -

    The Web console supports the following Console API messages:

    +

    The Web console supports the following Console API messages:

    The console prints a stack trace for all error messages, like this:

    diff --git a/files/en-us/tools/web_console/helpers/index.html b/files/en-us/tools/web_console/helpers/index.html index c9176537e0e90b5..cb9e4afebe580ca 100644 --- a/files/en-us/tools/web_console/helpers/index.html +++ b/files/en-us/tools/web_console/helpers/index.html @@ -101,7 +101,7 @@
    Given an object, returns a list of the values on that object; serves as a companion to keys().
    -

    Please refer to the Console API for more information about logging from content.

    +

    Please refer to the Console API for more information about logging from content.

    Variables

    @@ -125,5 +125,5 @@

    Looking at the contents of a 

    See also

    diff --git a/files/en-us/tools/web_console/remoting/index.html b/files/en-us/tools/web_console/remoting/index.html index d77a114c3aa857a..7858c21d85ea209 100644 --- a/files/en-us/tools/web_console/remoting/index.html +++ b/files/en-us/tools/web_console/remoting/index.html @@ -295,7 +295,7 @@

    Page errors

    Console API messages

    -

    The window.console API calls send internal messages throughout Gecko which allow us to do whatever we want for each call. The Web Console actor sends these messages to the remote debugging client.

    +

    The window.console API calls send internal messages throughout Gecko which allow us to do whatever we want for each call. The Web Console actor sends these messages to the remote debugging client.

    We use the ObjectActor from dbg-script-actors.js without a ThreadActor, to avoid slowing down the page scripts - the debugger deoptimizes JavaScript execution in the target page. The lifetime of object actors in the Web Console is different than the lifetime of these objects in the debugger - which is usually per pause or per thread. The Web Console manages the lifetime of ObjectActors manually.

    diff --git a/files/en-us/web/api/workerglobalscope/console/index.html b/files/en-us/web/api/workerglobalscope/console/index.html index 9b31c651d51ff21..dd38d5f1b9294d7 100644 --- a/files/en-us/web/api/workerglobalscope/console/index.html +++ b/files/en-us/web/api/workerglobalscope/console/index.html @@ -12,7 +12,7 @@ ---

    {{APIRef("Web Workers API")}}{{Non-standard_header}}

    -

    The console read-only property of the {{domxref("WorkerGlobalScope")}} interface returns a {{domxref("Console")}} object providing access to the browser console for the worker.

    +

    The console read-only property of the {{domxref("WorkerGlobalScope")}} interface returns a {{domxref("console")}} object providing access to the browser console for the worker.

    Syntax

    diff --git a/files/en-us/web/javascript/reference/global_objects/array/foreach/index.html b/files/en-us/web/javascript/reference/global_objects/array/foreach/index.html index 7c61fcee9b1b844..bc34ebd977f5b48 100644 --- a/files/en-us/web/javascript/reference/global_objects/array/foreach/index.html +++ b/files/en-us/web/javascript/reference/global_objects/array/foreach/index.html @@ -266,7 +266,7 @@

    Printing the contents of an array

    Note: In order to display the content of an array in the console, - you can use {{domxref("Console/table", "console.table()")}}, which prints a formatted + you can use {{domxref("console/table", "console.table()")}}, which prints a formatted version of the array.

    The following example illustrates an alternative approach, using