Merge branch 'mdn:main' into main

.github/workflows/interfacedata-updater.yml

@@ -19,7 +19,7 @@ jobs:
  ref: main
 
  - name: Setup node.js
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: "mdn-content/.nvmrc"
 

.github/workflows/markdown-lint-fix.yml

@@ -14,7 +14,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/markdown-lint.yml

@@ -21,7 +21,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/on-demand-preview-build.yml

@@ -27,7 +27,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/pr-check-lint_content.yml

@@ -63,7 +63,7 @@ jobs:
 
  - name: Setup Node.js environment
  if: ${{ env.DIFF_DOCUMENTS }}
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/pr-check_javascript.yml

@@ -18,7 +18,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/pr-check_json.yml

@@ -18,7 +18,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/pr-check_redirects.yml

@@ -13,7 +13,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/pr-check_scripts.yml

@@ -18,7 +18,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn
@@ -38,7 +38,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn
@@ -78,7 +78,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn
@@ -98,7 +98,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn
@@ -118,7 +118,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/pr-check_yml.yml

@@ -18,7 +18,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

.github/workflows/pr-test.yml

@@ -27,7 +27,7 @@ jobs:
  - uses: actions/checkout@v4
 
  - name: Setup Node.js environment
- uses: actions/setup-node@v3
+ uses: actions/setup-node@v4
  with:
  node-version-file: ".nvmrc"
  cache: yarn

files/en-us/_redirects.txt

@@ -7777,6 +7777,7 @@
 /en-US/docs/Web/API/CanvasRenderingContext2D/mozImageSmoothingEnabled /en-US/docs/Web/API/CanvasRenderingContext2D/imageSmoothingEnabled
 /en-US/docs/Web/API/CanvasRenderingContext2D/mozTextStyle /en-US/docs/Web/API/CanvasRenderingContext2D/font
 /en-US/docs/Web/API/Canvas_API/Drawing_graphics_with_canvas /en-US/docs/Web/API/Canvas_API/Tutorial
+/en-US/docs/Web/API/Canvas_API/Tutorial/Compositing/Example /en-US/docs/Web/API/CanvasRenderingContext2D/globalCompositeOperation
 /en-US/docs/Web/API/CharacterData.previousElementSibling /en-US/docs/Web/API/CharacterData/previousElementSibling
 /en-US/docs/Web/API/ChildNode.nextElementSibling /en-US/docs/Web/API/Element/nextElementSibling
 /en-US/docs/Web/API/ChildNode.remove /en-US/docs/Web/API/Element/remove
@@ -12034,7 +12035,7 @@
 /en-US/docs/Web/Guide/HTML/Canvas_tutorial/Basic_animations /en-US/docs/Web/API/Canvas_API/Tutorial/Basic_animations
 /en-US/docs/Web/Guide/HTML/Canvas_tutorial/Basic_usage /en-US/docs/Web/API/Canvas_API/Tutorial/Basic_usage
 /en-US/docs/Web/Guide/HTML/Canvas_tutorial/Compositing /en-US/docs/Web/API/Canvas_API/Tutorial/Compositing
-/en-US/docs/Web/Guide/HTML/Canvas_tutorial/Compositing/Example /en-US/docs/Web/API/Canvas_API/Tutorial/Compositing/Example
+/en-US/docs/Web/Guide/HTML/Canvas_tutorial/Compositing/Example /en-US/docs/Web/API/CanvasRenderingContext2D/globalCompositeOperation
 /en-US/docs/Web/Guide/HTML/Canvas_tutorial/Drawing_shapes /en-US/docs/Web/API/Canvas_API/Tutorial/Drawing_shapes
 /en-US/docs/Web/Guide/HTML/Canvas_tutorial/Optimizing_canvas /en-US/docs/Web/API/Canvas_API/Tutorial/Optimizing_canvas
 /en-US/docs/Web/Guide/HTML/Canvas_tutorial/Pixel_manipulation_with_canvas /en-US/docs/Web/API/Canvas_API/Tutorial/Pixel_manipulation_with_canvas

files/en-us/_wikihistory.json

@@ -24687,10 +24687,6 @@
  "trevorh"
  ]
  },
- "Web/API/Canvas_API/Tutorial/Compositing/Example": {
- "modified": "2019-03-23T23:28:23.382Z",
- "contributors": ["brttd", "beaugunderson", "jpmedley", "fscholz", "Sheppy"]
- },
  "Web/API/Canvas_API/Tutorial/Drawing_shapes": {
  "modified": "2020-08-05T11:19:13.950Z",
  "contributors": [

files/en-us/games/techniques/control_mechanisms/mobile_touch/index.md

@@ -8,7 +8,7 @@ page-type: guide
 
 {{NextMenu("Games/Techniques/Control_mechanisms/Desktop_with_mouse_and_keyboard", "Games/Techniques/Control_mechanisms")}}
 
-The future of mobile gaming is definitely web, and many developers choose the [mobile first](/en-US/docs/Web/Apps/Mobile_First) approach in their game development process — in the modern world, this generally also involves implementing touch controls. In this tutorial, we will see how easy it is to implement mobile controls in an HTML game, and enjoy playing on a mobile touch-enabled device.
+The future of mobile gaming is definitely web, and many developers choose the [mobile first](/en-US/docs/Glossary/Mobile_First) approach in their game development process — in the modern world, this generally also involves implementing touch controls. In this tutorial, we will see how easy it is to implement mobile controls in an HTML game, and enjoy playing on a mobile touch-enabled device.
 
 > **Note:** The game [Captain Rogers: Battle at Andromeda](https://rogers2.enclavegames.com/demo/) is built with Phaser and managing the controls is Phaser-based, but it could also be done in pure JavaScript. The good thing about using Phaser is that it offers helper variables and functions for easier and faster development, but it's entirely up to you which approach you to choose.
 

files/en-us/learn/accessibility/accessibility_troubleshooting/index.md

@@ -31,15 +31,15 @@ In the assessment for this module, we present to you a simple site with a number
 
 To get this assessment started, you should go and grab the [ZIP containing the files that comprise the example](https://raw.githubusercontent.com/mdn/learning-area/main/accessibility/assessment-start/assessment-files.zip). Decompress the contents into a new directory somewhere on your local computer.
 
-Alternatively, you could use a site like [JSBin](https://jsbin.com/) or [Glitch](https://glitch.com/) to do your assessment. You could paste the HTML, CSS, and JavaScript into one of these online editors. If the online editor you are using doesn't have a separate CSS/JS panel, feel free to put them in appropriate `<style>` / `<script>` elements.
+Alternatively, you could use an online editor such as [CodePen](https://codepen.io/), [JSFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/).
 
 The finished assessment site should look like so:
 
 ![Screenshot of the finished assessment site with good color contrast. The search input has placeholder text and a submit button that reads go, but no visible label.](assessment-site-finished.png)
 
 You will see some differences/issues with the display of the starting state of the assessment — this is mainly due to the differences in the markup, which in turn cause some styling issues as the CSS is not applied properly. Don't worry — you'll be fixing these problems in the upcoming sections!
 
-> **Note:** If you get stuck, then ask us for help — see the [Assessment or further help](#assessment_or_further_help) section at the bottom of this page.
+> **Note:** If you get stuck, you can reach out to us in one of our [communication channels](/en-US/docs/MDN/Community/Communication_channels).
 
 ## Project brief
 
@@ -83,16 +83,4 @@ The data table is not currently very accessible — it is hard for screen reader
 
 Can you list two more ideas for improvements that would make the website more accessible?
 
-## Assessment or further help
-
-If you would like your work assessed, or are stuck and want to ask for help:
-
-1. Put your work into an online shareable editor such as [CodePen](https://codepen.io/), [jsFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/).
-2. Write a post asking for assessment and/or help at the [MDN Discourse forum Learning category](https://discourse.mozilla.org/c/mdn/learn/250). Your post should include:
-
- - A descriptive title such as "Assessment wanted for Accessibility troubleshooting".
- - Details of what you have already tried, and what you would like us to do, e.g. if you are stuck and need help, or want an assessment.
- - A link to the example you want assessed or need help with, in an online shareable editor (as mentioned in step 1 above). This is a good practice to get into — it's very hard to help someone with a coding problem if you can't see their code.
- - A link to the actual task or assessment page, so we can find the question you want help with.
-
 {{PreviousMenu("Learn/Accessibility/Mobile", "Learn/Accessibility")}}

files/en-us/learn/accessibility/css_and_javascript/test_your_skills_colon__css_and_javascript_accessibility/index.md

@@ -8,9 +8,9 @@ page-type: learn-module-assessment
 
 The aim of this skill test is to assess whether you've understood our [CSS and JavaScript accessibility best practices](/en-US/docs/Learn/Accessibility/CSS_and_JavaScript) article.
 
-> **Note:** You can try out solutions in the interactive editors below, however it may be helpful to download the code and use an online tool such as [CodePen](https://codepen.io/), [jsFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/) to work on the tasks.
+> **Note:** You can try solutions in the interactive editors on this page or in an online editor such as [CodePen](https://codepen.io/), [JSFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/).
 >
-> If you get stuck, then ask us for help — see the [Assessment or further help](#assessment_or_further_help) section at the bottom of this page.
+> If you get stuck, you can reach out to us in one of our [communication channels](/en-US/docs/MDN/Community/Communication_channels).
 
 ## CSS accessibility 1
 
@@ -52,17 +52,3 @@ But it is not very accessible — in its current state you can only operate it w
 > **Callout:**
 >
 > [Download the starting point for this task](https://github.com/mdn/learning-area/blob/main/accessibility/tasks/js/js/js1-download.html) to work in your own editor or in an online editor.
-
-## Assessment or further help
-
-You can practice these examples in the Interactive Editors above.
-
-If you would like your work assessed, or are stuck and want to ask for help:
-
-1. Put your work into an online shareable editor such as [CodePen](https://codepen.io/), [jsFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/). You can write the code yourself, or use the starting point files linked to in the above sections.
-2. Write a post asking for assessment and/or help at the [MDN Discourse forum Learning category](https://discourse.mozilla.org/c/mdn/learn/250). Your post should include:
-
- - A descriptive title such as "Assessment wanted for CSS accessibility 1 skill test".
- - Details of what you have already tried, and what you would like us to do, e.g. if you are stuck and need help, or want an assessment.
- - A link to the example you want assessed or need help with, in an online shareable editor (as mentioned in step 1 above). This is a good practice to get into — it's very hard to help someone with a coding problem if you can't see their code.
- - A link to the actual task or assessment page, so we can find the question you want help with.

files/en-us/learn/accessibility/test_your_skills_colon__html_accessibility/index.md

@@ -8,9 +8,9 @@ page-type: learn-module-assessment
 
 The aim of this skill test is to assess whether you've understood our [HTML: A good basis for accessibility](/en-US/docs/Learn/Accessibility/HTML) article.
 
-> **Note:** You can try out solutions in the interactive editors below, however it may be helpful to download the code and use an online tool such as [CodePen](https://codepen.io/), [jsFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/) to work on the tasks.
+> **Note:** You can try solutions in the interactive editors on this page or in an online editor such as [CodePen](https://codepen.io/), [JSFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/).
 >
-> If you get stuck, then ask us for help — see the [Assessment or further help](#assessment_or_further_help) section at the bottom of this page.
+> If you get stuck, you can reach out to us in one of our [communication channels](/en-US/docs/MDN/Community/Communication_channels).
 
 ## HTML accessibility 1
 
@@ -72,17 +72,3 @@ Try updating the live code below to recreate the finished example:
 > **Callout:**
 >
 > [Download the starting point for this task](https://github.com/mdn/learning-area/blob/main/accessibility/tasks/html-css/html/html-a11y4-download.html) to work in your own editor or in an online editor.
-
-## Assessment or further help
-
-You can practice these examples in the Interactive Editors above.
-
-If you would like your work assessed, or are stuck and want to ask for help:
-
-1. Put your work into an online shareable editor such as [CodePen](https://codepen.io/), [jsFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/). You can write the code yourself, or use the starting point files linked to in the above sections.
-2. Write a post asking for assessment and/or help at the [MDN Discourse forum Learning category](https://discourse.mozilla.org/c/mdn/learn/250). Your post should include:
-
- - A descriptive title such as "Assessment wanted for HTML accessibility 1 skill test".
- - Details of what you have already tried, and what you would like us to do, e.g. if you are stuck and need help, or want an assessment.
- - A link to the example you want assessed or need help with, in an online shareable editor (as mentioned in step 1 above). This is a good practice to get into — it's very hard to help someone with a coding problem if you can't see their code.
- - A link to the actual task or assessment page, so we can find the question you want help with.

files/en-us/learn/accessibility/wai-aria_basics/test_your_skills_colon__wai-aria/index.md

@@ -8,9 +8,9 @@ page-type: learn-module-assessment
 
 The aim of this skill test is to assess whether you've understood our [WAI-ARIA basics](/en-US/docs/Learn/Accessibility/WAI-ARIA_basics) article.
 
-> **Note:** You can try out solutions in the interactive editors below, however it may be helpful to download the code and use an online tool such as [CodePen](https://codepen.io/), [jsFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/) to work on the tasks.
+> **Note:** You can try solutions in the interactive editors on this page or in an online editor such as [CodePen](https://codepen.io/), [JSFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/).
 >
-> If you get stuck, then ask us for help — see the [Assessment or further help](#assessment_or_further_help) section at the bottom of this page.
+> If you get stuck, you can reach out to us in one of our [communication channels](/en-US/docs/MDN/Community/Communication_channels).
 
 ## WAI-ARIA 1
 
@@ -48,17 +48,3 @@ The problem we have now is that when the DOM changes to show a new description,
 > **Callout:**
 >
 > [Download the starting point for this task](https://github.com/mdn/learning-area/blob/main/accessibility/tasks/js/aria/aria-js1-download.html) to work in your own editor or in an online editor.
-
-## Assessment or further help
-
-You can practice these examples in the Interactive Editors above.
-
-If you would like your work assessed, or are stuck and want to ask for help:
-
-1. Put your work into an online shareable editor such as [CodePen](https://codepen.io/), [jsFiddle](https://jsfiddle.net/), or [Glitch](https://glitch.com/). You can write the code yourself, or use the starting point files linked to in the above sections.
-2. Write a post asking for assessment and/or help at the [MDN Discourse forum Learning category](https://discourse.mozilla.org/c/mdn/learn/250). Your post should include:
-
- - A descriptive title such as "Assessment wanted for WAI-ARIA 1 skill test".
- - Details of what you have already tried, and what you would like us to do, e.g. if you are stuck and need help, or want an assessment.
- - A link to the example you want assessed or need help with, in an online shareable editor (as mentioned in step 1 above). This is a good practice to get into — it's very hard to help someone with a coding problem if you can't see their code.
- - A link to the actual task or assessment page, so we can find the question you want help with.