From 62d17528ce9736a5e827f1d72d3cbab668e45da1 Mon Sep 17 00:00:00 2001 From: Himanshu Date: Wed, 25 Dec 2024 22:59:41 +0530 Subject: [PATCH 001/265] fixes #37338. closes li tags (#37362) fixes 37338. closes li tags --- .../core/structuring_content/table_accessibility/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/files/en-us/learn_web_development/core/structuring_content/table_accessibility/index.md b/files/en-us/learn_web_development/core/structuring_content/table_accessibility/index.md index 3a4801bbb43ec32..67e5f223cb4d376 100644 --- a/files/en-us/learn_web_development/core/structuring_content/table_accessibility/index.md +++ b/files/en-us/learn_web_development/core/structuring_content/table_accessibility/index.md @@ -25,8 +25,8 @@ In the previous article, we looked at one of the most important features for mak Learning outcomes: From 3d10d0f1bd7f412dbdf759613c79da7711ce8261 Mon Sep 17 00:00:00 2001 From: Rohini Ranjan <109434545+rohini-ranjanR@users.noreply.github.com> Date: Thu, 26 Dec 2024 05:18:05 +0530 Subject: [PATCH 002/265] replace uses of alert() (#37373) --- files/en-us/web/api/htmlinputelement/showpicker/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/htmlinputelement/showpicker/index.md b/files/en-us/web/api/htmlinputelement/showpicker/index.md index 873bf06814c3e0d..e6eb87a502a5ac1 100644 --- a/files/en-us/web/api/htmlinputelement/showpicker/index.md +++ b/files/en-us/web/api/htmlinputelement/showpicker/index.md @@ -89,7 +89,7 @@ document.querySelectorAll("button").forEach((button) => { try { input.showPicker(); } catch (error) { - window.alert(error); + console.log(error); } }); }); From 4533daae74a7fdf41d70af9c66af5764decb4bdb Mon Sep 17 00:00:00 2001 From: Serhii Pustovit Date: Thu, 26 Dec 2024 03:32:40 +0200 Subject: [PATCH 003/265] Fix typo in `WebGLContextEvent` page `index.md` (#37374) --- files/en-us/web/api/webglcontextevent/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/webglcontextevent/index.md b/files/en-us/web/api/webglcontextevent/index.md index fbd8140c1f29268..2ca8fde1a6da33e 100644 --- a/files/en-us/web/api/webglcontextevent/index.md +++ b/files/en-us/web/api/webglcontextevent/index.md @@ -7,7 +7,7 @@ browser-compat: api.WebGLContextEvent {{APIRef("WebGL")}}{{AvailableInWorkers}} -The **WebContextEvent** interface is part of the [WebGL API](/en-US/docs/Web/API/WebGL_API) and is an interface for an event that is generated in response to a status change to the WebGL rendering context. +The **WebGLContextEvent** interface is part of the [WebGL API](/en-US/docs/Web/API/WebGL_API) and is an interface for an event that is generated in response to a status change to the WebGL rendering context. {{InheritanceDiagram}} From 07efed5a3d9e0e353d21db727247984f7e0ec051 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Thu, 26 Dec 2024 14:28:49 +0000 Subject: [PATCH 004/265] Bump markdownlint-cli2 from 0.16.0 to 0.17.0 (#37379) --- package.json | 2 +- yarn.lock | 108 ++++++++++++++++++++++++++++++++++++++++++--------- 2 files changed, 91 insertions(+), 19 deletions(-) diff --git a/package.json b/package.json index 925e40935c95197..2f7bae4d0106db4 100644 --- a/package.json +++ b/package.json @@ -55,7 +55,7 @@ "husky": "9.1.7", "js-yaml": "^4.1.0", "lint-staged": "15.2.11", - "markdownlint-cli2": "0.16.0", + "markdownlint-cli2": "0.17.0", "markdownlint-rule-search-replace": "1.2.0", "prettier": "3.4.2" }, diff --git a/yarn.lock b/yarn.lock index 5088dfa2d4d9437..f5e0fe0ef46058f 100644 --- a/yarn.lock +++ b/yarn.lock @@ -1668,6 +1668,11 @@ resolved "https://registry.yarnpkg.com/@types/json-schema/-/json-schema-7.0.15.tgz#596a1747233694d50f6ad8a7869fcb6f56cf5841" integrity sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA== +"@types/katex@^0.16.0": + version "0.16.7" + resolved "https://registry.yarnpkg.com/@types/katex/-/katex-0.16.7.tgz#03ab680ab4fa4fbc6cb46ecf987ecad5d8019868" + integrity sha512-HMwFiRujE5PjrgwHQ25+bsLJgowjGjm5Z8FVSf0N6PwgJrwxH0QxzHYDcKsTfV3wva0vzrpqMTJS2jXPr5BMEQ== + "@types/lodash@^4.14.149": version "4.17.7" resolved "https://registry.yarnpkg.com/@types/lodash/-/lodash-4.17.7.tgz#2f776bcb53adc9e13b2c0dfd493dfcbd7de43612" @@ -2729,6 +2734,11 @@ commander@^7.2.0: resolved "https://registry.yarnpkg.com/commander/-/commander-7.2.0.tgz#a36cb57d0b501ce108e4d20559a150a391d97ab7" integrity sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw== +commander@^8.3.0: + version "8.3.0" + resolved "https://registry.yarnpkg.com/commander/-/commander-8.3.0.tgz#4837ea1b2da67b9c616a67afbb0fafee567bca66" + integrity sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww== + commander@~12.1.0: version "12.1.0" resolved "https://registry.yarnpkg.com/commander/-/commander-12.1.0.tgz#01423b36f501259fdaac4d0e4d60c96c991585d3" @@ -5528,6 +5538,13 @@ junk@^4.0.1: resolved "https://registry.yarnpkg.com/junk/-/junk-4.0.1.tgz#7ee31f876388c05177fe36529ee714b07b50fbed" integrity sha512-Qush0uP+G8ZScpGMZvHUiRfI0YBWuB3gVBYlI0v0vvOJt5FLicco+IkP0a50LqTTQhmts/m6tP5SWE+USyIvcQ== +katex@^0.16.0: + version "0.16.18" + resolved "https://registry.yarnpkg.com/katex/-/katex-0.16.18.tgz#20781284288bc52805c519e48ac756163ad4b1f3" + integrity sha512-LRuk0rPdXrecAFwQucYjMiIs0JFefk6N1q/04mlw14aVIVgxq1FO0MA9RiIIGVaKOB5GIP5GH4aBBNraZERmaQ== + dependencies: + commander "^8.3.0" + keyv@3.0.0: version "3.0.0" resolved "https://registry.yarnpkg.com/keyv/-/keyv-3.0.0.tgz#44923ba39e68b12a7cec7df6c3268c031f2ef373" @@ -5824,23 +5841,18 @@ markdownlint-cli2-formatter-default@0.0.5: resolved "https://registry.yarnpkg.com/markdownlint-cli2-formatter-default/-/markdownlint-cli2-formatter-default-0.0.5.tgz#b8fde4e127f9a9c0596e6d45eed352dd0aa0ff98" integrity sha512-4XKTwQ5m1+Txo2kuQ3Jgpo/KmnG+X90dWt4acufg6HVGadTUG5hzHF/wssp9b5MBYOMCnZ9RMPaU//uHsszF8Q== -markdownlint-cli2@0.16.0: - version "0.16.0" - resolved "https://registry.yarnpkg.com/markdownlint-cli2/-/markdownlint-cli2-0.16.0.tgz#95c599e28aff8e4286fbf08003e7fc1282ec0cac" - integrity sha512-oy5dJdOxGMKSwrlouxdEGf6N4O2Iz8oJ4/HO2Ix67o4vTK1AQNGjZUNwTIzfa5x+XbJ++dfgR1gLfILajsW+1Q== +markdownlint-cli2@0.17.0: + version "0.17.0" + resolved "https://registry.yarnpkg.com/markdownlint-cli2/-/markdownlint-cli2-0.17.0.tgz#1a93fa0c1708981a8f12b175e53d899fe7b448d1" + integrity sha512-8Xz7wkkkV4wJTf+pvryU3J/fT3BZWD3ZykcjYBR0GuH0GHvrCbswaCdurbuUuAPDGFZy4cxBGYCJSAOW8jM4aQ== dependencies: globby "14.0.2" js-yaml "4.1.0" jsonc-parser "3.3.1" - markdownlint "0.36.1" + markdownlint "0.37.2" markdownlint-cli2-formatter-default "0.0.5" micromatch "4.0.8" -markdownlint-micromark@0.1.12: - version "0.1.12" - resolved "https://registry.yarnpkg.com/markdownlint-micromark/-/markdownlint-micromark-0.1.12.tgz#8fc055f4588039654e5af75f1b9fc492da64c76a" - integrity sha512-RlB6EwMGgc0sxcIhOQ2+aq7Zw1V2fBnzbXKGgYK/mVWdT7cz34fteKSwfYeo4rL6+L/q2tyC9QtD/PgZbkdyJQ== - markdownlint-micromark@0.1.2: version "0.1.2" resolved "https://registry.yarnpkg.com/markdownlint-micromark/-/markdownlint-micromark-0.1.2.tgz#5520e04febffa46741875a2f297509ffdb561f5c" @@ -5860,13 +5872,19 @@ markdownlint-rule-search-replace@1.2.0: dependencies: markdownlint-rule-helpers "0.21.0" -markdownlint@0.36.1: - version "0.36.1" - resolved "https://registry.yarnpkg.com/markdownlint/-/markdownlint-0.36.1.tgz#86491d35ad6eda89e1290404850a574da3e64490" - integrity sha512-s73fU2CQN7WCgjhaQUQ8wYESQNzGRNOKDd+3xgVqu8kuTEhmwepd/mxOv1LR2oV046ONrTLBFsM7IoKWNvmy5g== +markdownlint@0.37.2: + version "0.37.2" + resolved "https://registry.yarnpkg.com/markdownlint/-/markdownlint-0.37.2.tgz#72461a7abfef2e01ae7f3b596cdc083a25856571" + integrity sha512-m8QhYnRA1ptbhIjhVVBUkKQcUelVxuyO/yXyLewnc1+xs4eXhST/+hIy29goO+EYVLmWtknH4SmYQ4s0caoKqw== dependencies: markdown-it "14.1.0" - markdownlint-micromark "0.1.12" + micromark "4.0.1" + micromark-extension-directive "3.0.2" + micromark-extension-gfm-autolink-literal "2.1.0" + micromark-extension-gfm-footnote "2.1.0" + micromark-extension-gfm-table "2.1.0" + micromark-extension-math "3.1.0" + micromark-util-types "2.0.1" md5-file@^5.0.0: version "5.0.0" @@ -6119,7 +6137,20 @@ micromark-core-commonmark@^2.0.0: micromark-util-symbol "^2.0.0" micromark-util-types "^2.0.0" -micromark-extension-gfm-autolink-literal@^2.0.0: +micromark-extension-directive@3.0.2: + version "3.0.2" + resolved "https://registry.yarnpkg.com/micromark-extension-directive/-/micromark-extension-directive-3.0.2.tgz#2eb61985d1995a7c1ff7621676a4f32af29409e8" + integrity sha512-wjcXHgk+PPdmvR58Le9d7zQYWy+vKEU9Se44p2CrCDPiLr2FMyiT4Fyb5UFKFC66wGB3kPlgD7q3TnoqPS7SZA== + dependencies: + devlop "^1.0.0" + micromark-factory-space "^2.0.0" + micromark-factory-whitespace "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + parse-entities "^4.0.0" + +micromark-extension-gfm-autolink-literal@2.1.0, micromark-extension-gfm-autolink-literal@^2.0.0: version "2.1.0" resolved "https://registry.yarnpkg.com/micromark-extension-gfm-autolink-literal/-/micromark-extension-gfm-autolink-literal-2.1.0.tgz#6286aee9686c4462c1e3552a9d505feddceeb935" integrity sha512-oOg7knzhicgQ3t4QCjCWgTmfNhvQbDDnJeVu9v81r7NltNCVmhPy1fJRX27pISafdjL+SVc4d3l48Gb6pbRypw== @@ -6129,7 +6160,7 @@ micromark-extension-gfm-autolink-literal@^2.0.0: micromark-util-symbol "^2.0.0" micromark-util-types "^2.0.0" -micromark-extension-gfm-footnote@^2.0.0: +micromark-extension-gfm-footnote@2.1.0, micromark-extension-gfm-footnote@^2.0.0: version "2.1.0" resolved "https://registry.yarnpkg.com/micromark-extension-gfm-footnote/-/micromark-extension-gfm-footnote-2.1.0.tgz#4dab56d4e398b9853f6fe4efac4fc9361f3e0750" integrity sha512-/yPhxI1ntnDNsiHtzLKYnE3vf9JZ6cAisqVDauhp4CEHxlb4uoOTxOCJ+9s51bIB8U1N1FJ1RXOKTIlD5B/gqw== @@ -6155,7 +6186,7 @@ micromark-extension-gfm-strikethrough@^2.0.0: micromark-util-symbol "^2.0.0" micromark-util-types "^2.0.0" -micromark-extension-gfm-table@^2.0.0: +micromark-extension-gfm-table@2.1.0, micromark-extension-gfm-table@^2.0.0: version "2.1.0" resolved "https://registry.yarnpkg.com/micromark-extension-gfm-table/-/micromark-extension-gfm-table-2.1.0.tgz#5cadedfbb29fca7abf752447967003dc3b6583c9" integrity sha512-Ub2ncQv+fwD70/l4ou27b4YzfNaCJOvyX4HxXU15m7mpYY+rjuWzsLIPZHJL253Z643RpbcP1oeIJlQ/SKW67g== @@ -6198,6 +6229,19 @@ micromark-extension-gfm@^3.0.0: micromark-util-combine-extensions "^2.0.0" micromark-util-types "^2.0.0" +micromark-extension-math@3.1.0: + version "3.1.0" + resolved "https://registry.yarnpkg.com/micromark-extension-math/-/micromark-extension-math-3.1.0.tgz#c42ee3b1dd5a9a03584e83dd8f08e3de510212c1" + integrity sha512-lvEqd+fHjATVs+2v/8kg9i5Q0AP2k85H0WUOwpIVvUML8BapsMvh1XAogmQjOCsLpoKRCVQqEkQBB3NhVBcsOg== + dependencies: + "@types/katex" "^0.16.0" + devlop "^1.0.0" + katex "^0.16.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + micromark-factory-destination@^2.0.0: version "2.0.0" resolved "https://registry.yarnpkg.com/micromark-factory-destination/-/micromark-factory-destination-2.0.0.tgz#857c94debd2c873cba34e0445ab26b74f6a6ec07" @@ -6342,11 +6386,39 @@ micromark-util-symbol@^2.0.0: resolved "https://registry.yarnpkg.com/micromark-util-symbol/-/micromark-util-symbol-2.0.0.tgz#12225c8f95edf8b17254e47080ce0862d5db8044" integrity sha512-8JZt9ElZ5kyTnO94muPxIGS8oyElRJaiJO8EzV6ZSyGQ1Is8xwl4Q45qU5UOg+bGH4AikWziz0iN4sFLWs8PGw== +micromark-util-types@2.0.1: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-types/-/micromark-util-types-2.0.1.tgz#a3edfda3022c6c6b55bfb049ef5b75d70af50709" + integrity sha512-534m2WhVTddrcKVepwmVEVnUAmtrx9bfIjNoQHRqfnvdaHQiFytEhJoTgpWJvDEXCO5gLTQh3wYC1PgOJA4NSQ== + micromark-util-types@^2.0.0: version "2.0.0" resolved "https://registry.yarnpkg.com/micromark-util-types/-/micromark-util-types-2.0.0.tgz#63b4b7ffeb35d3ecf50d1ca20e68fc7caa36d95e" integrity sha512-oNh6S2WMHWRZrmutsRmDDfkzKtxF+bc2VxLC9dvtrDIRFln627VsFP6fLMgTryGDljgLPjkrzQSDcPrjPyDJ5w== +micromark@4.0.1: + version "4.0.1" + resolved "https://registry.yarnpkg.com/micromark/-/micromark-4.0.1.tgz#294c2f12364759e5f9e925a767ae3dfde72223ff" + integrity sha512-eBPdkcoCNvYcxQOAKAlceo5SNdzZWfF+FcSupREAzdAh9rRmE239CEQAiTwIgblwnoM8zzj35sZ5ZwvSEOF6Kw== + dependencies: + "@types/debug" "^4.0.0" + debug "^4.0.0" + decode-named-character-reference "^1.0.0" + devlop "^1.0.0" + micromark-core-commonmark "^2.0.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-chunked "^2.0.0" + micromark-util-combine-extensions "^2.0.0" + micromark-util-decode-numeric-character-reference "^2.0.0" + micromark-util-encode "^2.0.0" + micromark-util-normalize-identifier "^2.0.0" + micromark-util-resolve-all "^2.0.0" + micromark-util-sanitize-uri "^2.0.0" + micromark-util-subtokenize "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + micromark@^4.0.0: version "4.0.0" resolved "https://registry.yarnpkg.com/micromark/-/micromark-4.0.0.tgz#84746a249ebd904d9658cfabc1e8e5f32cbc6249" From adc6269e8968d43e9571a560f0f452ffd0ea17c1 Mon Sep 17 00:00:00 2001 From: Kylo <56988649+Kylo33@users.noreply.github.com> Date: Thu, 26 Dec 2024 19:54:17 -0700 Subject: [PATCH 005/265] Fix typo on 'HTML: Creating the content' page (#37324) --- .../your_first_website/creating_the_content/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/learn_web_development/getting_started/your_first_website/creating_the_content/index.md b/files/en-us/learn_web_development/getting_started/your_first_website/creating_the_content/index.md index 541f2ebb8b0dc95..2af7d144a658776 100644 --- a/files/en-us/learn_web_development/getting_started/your_first_website/creating_the_content/index.md +++ b/files/en-us/learn_web_development/getting_started/your_first_website/creating_the_content/index.md @@ -156,7 +156,7 @@ The keywords for alt text are "descriptive text". The alt text you write should Let's get your image displaying now. 1. Inside the `first-website` folder, Create a new folder called `images`, and put the image you chose in the previous example inside this folder. -2. Inside the `` tag's `alt` attribute value, enter the path to your image. It is inside a folder called `images`, which is inside the same directory as your `index.html` file, therefore the path will be `images/` plus the name of your image. For example, if your image was called `firefox-icon.png`, your `src` attribute would look like this: `src="images/firefox-icon.png"`. +2. Inside the `` tag's `src` attribute value, enter the path to your image. It is inside a folder called `images`, which is inside the same directory as your `index.html` file, therefore the path will be `images/` plus the name of your image. For example, if your image was called `firefox-icon.png`, your `src` attribute would look like this: `src="images/firefox-icon.png"`. 3. replace the `alt` attribute value — `My test image` — with some text that better describes your image. 4. Open your `index.html` file inside a web browser. You should see your image displayed. If not, check your `` element against our code above; make sure it is not missing any of the syntax, such as the quote marks. Make sure the image filename is correct. From 757b1038d7f81c91e61788f4060c9151bd0fda20 Mon Sep 17 00:00:00 2001 From: Dhyan Rai <172551908+raaid3@users.noreply.github.com> Date: Thu, 26 Dec 2024 23:07:19 -0500 Subject: [PATCH 006/265] Fix minor typo (#37385) --- .../core/styling_basics/values_and_units/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/learn_web_development/core/styling_basics/values_and_units/index.md b/files/en-us/learn_web_development/core/styling_basics/values_and_units/index.md index 2c4b3fb81afe275..3beb6dabebec850 100644 --- a/files/en-us/learn_web_development/core/styling_basics/values_and_units/index.md +++ b/files/en-us/learn_web_development/core/styling_basics/values_and_units/index.md @@ -43,7 +43,7 @@ In this lesson, we will take a look at some of the most frequently used value ty In CSS specifications and on the property pages here on MDN you will be able to spot value types as they will be surrounded by angle brackets (`<`, `>`), such as [``](/en-US/docs/Web/CSS/color_value) or {{cssxref("length")}}. When you see the value type `` as valid for a particular property, that means you can use any valid color as a value for that property, as listed on the [``](/en-US/docs/Web/CSS/color_value) reference page. -Sometimes value types and properties can have the same, or similar names — For example, there is a {{cssxref("color")}} property and a [``](/en-US/docs/Web/CSS/color_value) data type. You can use the angle brackets to determine which one you are studying in each case. HTML elements also use angle brackets, but it should be clear from the context which one you are looking at. If yo are not sure, try searching for it on MDN. +Sometimes value types and properties can have the same, or similar names — For example, there is a {{cssxref("color")}} property and a [``](/en-US/docs/Web/CSS/color_value) data type. You can use the angle brackets to determine which one you are studying in each case. HTML elements also use angle brackets, but it should be clear from the context which one you are looking at. If you are not sure, try searching for it on MDN. > [!NOTE] > You'll see CSS value types referred to as _data types_. The terms are basically interchangeable — when you see something in CSS referred to as a data type, it is really just a fancy way of saying value type. The term _value_ refers to any particular expression supported by a value type that you choose to use. From 9575097ee96531811fb8af7dd5f5e103cacf653d Mon Sep 17 00:00:00 2001 From: Ben Richeson <36977340+Benricheson101@users.noreply.github.com> Date: Fri, 27 Dec 2024 22:41:09 -0500 Subject: [PATCH 007/265] Fix typo in Set union Venn diagram alt text (#37391) fix: Set union alt text --- .../en-us/web/javascript/reference/global_objects/set/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/javascript/reference/global_objects/set/index.md b/files/en-us/web/javascript/reference/global_objects/set/index.md index 6a6090f55ca8ee9..692d7516065c47d 100644 --- a/files/en-us/web/javascript/reference/global_objects/set/index.md +++ b/files/en-us/web/javascript/reference/global_objects/set/index.md @@ -67,7 +67,7 @@ The `Set` object provides some methods that allow you to compose sets like you w A∪BA\cup B - A Venn diagram where two circles overlap. The symmetric difference of A and B is the region contained by either or both circles. + A Venn diagram where two circles overlap. The union of A and B is the region contained by either or both circles. {{jsxref("Set/isDisjointFrom", "A.isDisjointFrom(B)")}} From 52131aa028ff9360b11c55d29d9dadaf03aabfae Mon Sep 17 00:00:00 2001 From: Onkar Khadangale <87750369+OnkarRuikar@users.noreply.github.com> Date: Sat, 28 Dec 2024 09:13:44 +0530 Subject: [PATCH 008/265] fix(ci): improve logging in the reviewdog workflow (#37292) * fix(ci): improve logging in the reviewdog workflow * add one line separation in logs * Update .github/workflows/pr-check-lint_content.yml Co-authored-by: Joshua Chen --------- Co-authored-by: Joshua Chen --- .github/workflows/pr-check-lint_content.yml | 45 ++++++++++++++++---- .vscode/dictionaries/terms-abbreviations.txt | 4 ++ 2 files changed, 40 insertions(+), 9 deletions(-) diff --git a/.github/workflows/pr-check-lint_content.yml b/.github/workflows/pr-check-lint_content.yml index a505197e579fac8..d9ee293eb809f54 100644 --- a/.github/workflows/pr-check-lint_content.yml +++ b/.github/workflows/pr-check-lint_content.yml @@ -101,6 +101,12 @@ jobs: echo "FM_LINT_FAILED=${FM_LINT_FAILED}" >> $GITHUB_ENV echo "Running Prettier" + PRETTIER_FAILED=false + PRETTIER_LOG=$(yarn prettier --check ${files_to_lint} 2>&1) || PRETTIER_FAILED=true + echo "PRETTIER_LOG<<${EOF}" >> $GITHUB_ENV + echo "${PRETTIER_LOG}" >> $GITHUB_ENV + echo "${EOF}" >> $GITHUB_ENV + echo "PRETTIER_FAILED=${PRETTIER_FAILED}" >> $GITHUB_ENV yarn prettier -w ${files_to_lint} if [[ -n $(git diff) ]]; then @@ -110,16 +116,17 @@ jobs: # info for troubleshooting echo MD_LINT_FAILED=${MD_LINT_FAILED} echo FM_LINT_FAILED=${FM_LINT_FAILED} + echo PRETTIER_FAILED=${PRETTIER_FAILED} git diff - name: Setup reviewdog - if: env.FILES_MODIFIED == 'true' || env.MD_LINT_FAILED == 'true' + if: ${{ env.FILES_MODIFIED == 'true' || env.MD_LINT_FAILED == 'true' }} uses: reviewdog/action-setup@v1 with: reviewdog_version: latest - name: Suggest changes using diff - if: env.FILES_MODIFIED == 'true' + if: ${{ env.FILES_MODIFIED == 'true' }} env: REVIEWDOG_GITHUB_API_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | @@ -134,7 +141,7 @@ jobs: -reporter=github-pr-review < "${TMPFILE}" - name: Add reviews for markdownlint errors - if: env.MD_LINT_FAILED == 'true' + if: ${{ env.MD_LINT_FAILED == 'true' }} env: REVIEWDOG_GITHUB_API_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | @@ -147,11 +154,31 @@ jobs: -reporter="github-pr-review" - name: Fail if any issues pending - if: env.FILES_MODIFIED == 'true' || env.MD_LINT_FAILED == 'true' || env.FM_LINT_FAILED == 'true' + if: ${{ env.FILES_MODIFIED == 'true' || env.MD_LINT_FAILED == 'true' || env.FM_LINT_FAILED == 'true' }} + env: + MD_LINT_FAILED: ${{ env.MD_LINT_FAILED }} + FM_LINT_FAILED: ${{ env.FM_LINT_FAILED }} + PRETTIER_FAILED: ${{ env.PRETTIER_FAILED }} + MD_LINT_LOG: ${{ env.MD_LINT_LOG }} + FM_LINT_LOG: ${{ env.FM_LINT_LOG }} + PRETTIER_LOG: ${{ env.PRETTIER_LOG }} run: | - echo -e "\nLogs from markdownlint:" - echo "${MD_LINT_LOG}" - echo -e "\nLogs from front-matter linter:" - echo "${FM_LINT_LOG}" - echo -e "\nPlease fix all the linting issues mentioned in above logs and in the review comments." + echo -e "\nPlease fix all the linting issues mentioned in the following logs and in the PR review comments." + + if [[ ${MD_LINT_FAILED} == 'true' ]]; then + echo -e "\n\n🪵 Logs from markdownlint:" + echo "${MD_LINT_LOG}" + fi + + if [[ ${FM_LINT_FAILED} == 'true' ]]; then + echo -e "\n\n🪵 Logs from front-matter linter:" + echo "${FM_LINT_LOG}" + fi + + if [[ ${PRETTIER_FAILED} == 'true' ]]; then + echo -e "\n\n🪵 Logs from Prettier formatter:" + echo "${PRETTIER_LOG}" + echo -e "\nYou can use Prettier playground to format the files online (configuration pre-filled): https://prettier.io/playground/#N4Igxg9gdgLgprEAuEBiABABwIYGd7owAWc6CMAlgE6kBmFANqSTSADQgSaXS7KjYqVCAHcACoIR8U2BiOwBPPhwBGVbGADWcGAGVsAWzgAZClDjIYVAK5xV6rTt04wZgOaWbdkLjgGKnrYccAAemHBUFEawsgAqEVCCFHDStLK+HLjuTACK1hDwyGkMGSAAVrghutlweQUWSMWlAI758GLCmNIgeAC05nAAJkPsIFbYjO4AwhAGBtjIPQwMo1lQbkwAgjBWFCrW7RGm5kXp3kQwBgwA6kQU8LgucLpS9xQAbvcKi2C4yiDvWwASSgw1gujAkW4m1BuhgCiYpxK3kwwl813UmEWqJSEXeFg4Zl8VBgHWwbnmSNKOCoxMW8yomkGoigo1RZhg1wog2IyAAHAAGDg0VrUOBkikLRpnDgwbAqLk8ojIABMHGsvli8tSMpAfhUQ2Gg2M2HW1nJcAAYhAqPMdu5FtgDhAQABfV1AA \n" + fi + exit 1 diff --git a/.vscode/dictionaries/terms-abbreviations.txt b/.vscode/dictionaries/terms-abbreviations.txt index a5ae1a6c676f117..511ee458ccbdf69 100644 --- a/.vscode/dictionaries/terms-abbreviations.txt +++ b/.vscode/dictionaries/terms-abbreviations.txt @@ -21,6 +21,7 @@ ANMF anonymization antialiasing antitracking +apideck APNG appcontent arcosh @@ -529,6 +530,7 @@ quickmenu qvalues QWERTZ randomizer +rari rasterizes RDBMS RDBMSes @@ -562,6 +564,7 @@ retarget retargeted retargeting retargetings +reviewdog RFCOMM RGTC roadmaps @@ -879,6 +882,7 @@ xrayed Xrays XRCPU XSSI +yari yearless Zalgo zoomable From 9066facc8584580afa066ddc3f23cff820e20b8f Mon Sep 17 00:00:00 2001 From: 60x20 <120422100+60x20@users.noreply.github.com> Date: Sat, 28 Dec 2024 06:47:19 +0300 Subject: [PATCH 009/265] Improve phrasing in Iterator.prototype.take() (#37389) * improve phrasing * add reference to `break` * Update files/en-us/web/javascript/reference/global_objects/iterator/take/index.md --------- Co-authored-by: Joshua Chen --- .../javascript/reference/global_objects/iterator/take/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/javascript/reference/global_objects/iterator/take/index.md b/files/en-us/web/javascript/reference/global_objects/iterator/take/index.md index 8bd5ef7159f4e23..20fda50574b65b2 100644 --- a/files/en-us/web/javascript/reference/global_objects/iterator/take/index.md +++ b/files/en-us/web/javascript/reference/global_objects/iterator/take/index.md @@ -69,7 +69,7 @@ for (const n of fibonacci().take(5)) { // 5 ``` -Because `fibonacci()` is an infinite iterator, you can't use a `for` loop to iterate it directly. +Because `fibonacci()` is an infinite iterator, using a `for` loop to iterate it without any logic to exit early (such as a {{jsxref("Statements/break", "break")}} statement) would result in an infinite loop. ### Combining drop() with take() From f0eaec89eaacf987e2212585868cbce62283d519 Mon Sep 17 00:00:00 2001 From: David Laban Date: Sat, 28 Dec 2024 04:19:06 +0000 Subject: [PATCH 010/265] signpost touch-action from the pointercancel event (#37388) --- files/en-us/web/api/pointer_events/index.md | 26 ++++++++++----------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/files/en-us/web/api/pointer_events/index.md b/files/en-us/web/api/pointer_events/index.md index 714847e8953dc30..b85c450f885869c 100644 --- a/files/en-us/web/api/pointer_events/index.md +++ b/files/en-us/web/api/pointer_events/index.md @@ -95,19 +95,19 @@ Pointer events have ten event types, seven of which have similar semantics to th Below is a short description of each event type. -| Event | Description | -| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {{domxref('Element/pointerover_event', 'pointerover')}} | Fired when a pointer is moved into an element's [hit test](#hit_test) boundaries. | -| {{domxref('Element/pointerenter_event', 'pointerenter')}} | Fired when a pointer is moved into the [hit test](#hit_test) boundaries of an element or one of its descendants, including as a result of a `pointerdown` event from a device that does not support hover (see `pointerdown`). | -| {{domxref('Element/pointerdown_event', 'pointerdown')}} | Fired when a pointer becomes _active buttons state_. | -| {{domxref('Element/pointermove_event', 'pointermove')}} | Fired when a pointer changes coordinates. This event is also used if the change in pointer state cannot be reported by other events. | -| {{domxref('Element/pointerup_event', 'pointerup')}} | Fired when a pointer is no longer _active buttons state_. | -| {{domxref('Element/pointercancel_event', 'pointercancel')}} | A browser fires this event if it concludes the pointer will no longer be able to generate events (for example the related device is deactivated). | -| {{domxref('Element/pointerout_event', 'pointerout')}} | Fired for several reasons including: pointer is moved out of the [hit test](#hit_test) boundaries of an element; firing the pointerup event for a device that does not support hover (see `pointerup`); after firing the `pointercancel` event (see `pointercancel`); when a pen stylus leaves the hover range detectable by the digitizer. | -| {{domxref('Element/pointerleave_event', 'pointerleave')}} | Fired when a pointer is moved out of the [hit test](#hit_test) boundaries of an element. For pen devices, this event is fired when the stylus leaves the hover range detectable by the digitizer. | -| {{domxref('Element/pointerrawupdate_event', 'pointerrawupdate')}} {{experimental_inline}} | Fired when a pointer changes any properties that don't fire `pointerdown` or `pointerup` events. | -| {{domxref('Element/gotpointercapture_event', 'gotpointercapture')}} | Fired when an element receives pointer capture. | -| {{domxref('Element/lostpointercapture_event', 'lostpointercapture')}} | Fired after pointer capture is released for a pointer. | +| Event | Description | +| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {{domxref('Element/pointerover_event', 'pointerover')}} | Fired when a pointer is moved into an element's [hit test](#hit_test) boundaries. | +| {{domxref('Element/pointerenter_event', 'pointerenter')}} | Fired when a pointer is moved into the [hit test](#hit_test) boundaries of an element or one of its descendants, including as a result of a `pointerdown` event from a device that does not support hover (see `pointerdown`). | +| {{domxref('Element/pointerdown_event', 'pointerdown')}} | Fired when a pointer becomes _active buttons state_. | +| {{domxref('Element/pointermove_event', 'pointermove')}} | Fired when a pointer changes coordinates. This event is also used if the change in pointer state cannot be reported by other events. | +| {{domxref('Element/pointerup_event', 'pointerup')}} | Fired when a pointer is no longer _active buttons state_. | +| {{domxref('Element/pointercancel_event', 'pointercancel')}} | A browser fires this event if it concludes the pointer will no longer be able to generate events (for example, if the related device is deactivated, or the browser decided to interpret the interaction as a pan/zoom instead). For information on how to control this behavior, see [the section on the `touch-action` CSS property](#touch-action_css_property) below. | +| {{domxref('Element/pointerout_event', 'pointerout')}} | Fired for several reasons including: pointer is moved out of the [hit test](#hit_test) boundaries of an element; firing the pointerup event for a device that does not support hover (see `pointerup`); after firing the `pointercancel` event (see `pointercancel`); when a pen stylus leaves the hover range detectable by the digitizer. | +| {{domxref('Element/pointerleave_event', 'pointerleave')}} | Fired when a pointer is moved out of the [hit test](#hit_test) boundaries of an element. For pen devices, this event is fired when the stylus leaves the hover range detectable by the digitizer. | +| {{domxref('Element/pointerrawupdate_event', 'pointerrawupdate')}} {{experimental_inline}} | Fired when a pointer changes any properties that don't fire `pointerdown` or `pointerup` events. | +| {{domxref('Element/gotpointercapture_event', 'gotpointercapture')}} | Fired when an element receives pointer capture. | +| {{domxref('Element/lostpointercapture_event', 'lostpointercapture')}} | Fired after pointer capture is released for a pointer. | ### Element extensions From c37011659ce69ad4615db4c07e758f9fcf7dcb23 Mon Sep 17 00:00:00 2001 From: skyclouds2001 <95597335+skyclouds2001@users.noreply.github.com> Date: Sun, 29 Dec 2024 02:28:39 +0800 Subject: [PATCH 011/265] Add & move Formal syntax section for css at-rule (#37346) * Add & move Formal syntax section for css at-rule * Update index.md --- files/en-us/web/css/@color-profile/index.md | 8 ++++---- files/en-us/web/css/@container/index.md | 4 ++++ files/en-us/web/css/@media/index.md | 8 ++++---- 3 files changed, 12 insertions(+), 8 deletions(-) diff --git a/files/en-us/web/css/@color-profile/index.md b/files/en-us/web/css/@color-profile/index.md index df869b201d01c36..2ccdb69c512c912 100644 --- a/files/en-us/web/css/@color-profile/index.md +++ b/files/en-us/web/css/@color-profile/index.md @@ -36,6 +36,10 @@ The **`@color-profile`** [CSS](/en-US/docs/Web/CSS) [at-rule](/en-US/docs/Web/CS - `saturation` - : This option was created to preserve the relative saturation (chroma) of the original, and to keep solid colors pure. However, it experienced interoperability problems like the perceptual intent. +## Formal syntax + +{{csssyntax}} + ## Examples This example is from the specification and demonstrates using offset printing to ISO 12647-2:2004 using the CGATS/SWOP TR005 2007 characterization data on grade 5 paper with an ink limit of 300% Total Area Coverage, and medium gray component replacement (GCR). @@ -51,10 +55,6 @@ The `src` descriptor specifies the URL to retrieve the color-profile information } ``` -## Formal syntax - -{{csssyntax}} - ## Specifications {{Specifications}} diff --git a/files/en-us/web/css/@container/index.md b/files/en-us/web/css/@container/index.md index 0bc5f0c101b4862..a36f9836ecc9072 100644 --- a/files/en-us/web/css/@container/index.md +++ b/files/en-us/web/css/@container/index.md @@ -148,6 +148,10 @@ The following descriptors can be used within the container condition: - `width` - : The width of the container expressed as a {{cssxref("length")}} value. +## Formal syntax + +{{csssyntax}} + ## Examples ### Setting styles based on a container's size diff --git a/files/en-us/web/css/@media/index.md b/files/en-us/web/css/@media/index.md index 96d82292f6f65d4..26db828a46c7c42 100644 --- a/files/en-us/web/css/@media/index.md +++ b/files/en-us/web/css/@media/index.md @@ -171,6 +171,10 @@ Some media queries have corresponding [user agent client hints](/en-US/docs/Web/ These are HTTP headers that request content that is pre-optimized for the particular media requirement. They include {{HTTPHeader("Sec-CH-Prefers-Color-Scheme")}} and {{HTTPHeader("Sec-CH-Prefers-Reduced-Motion")}}. +## Formal syntax + +{{csssyntax}} + ## Accessibility To best accommodate people who adjust a site's text size, use [`em`](/en-US/docs/Web/CSS/CSS_Values_and_Units#numeric_data_types)s when you need a {{cssxref("<length>")}} for your [media queries](/en-US/docs/Web/CSS/CSS_media_queries/Using_media_queries). @@ -186,10 +190,6 @@ Because media queries provide insights into the capabilities—and by extension, Because of this potential, a browser may opt to fudge the returned values in some manner in order to prevent them from being used to precisely identify a computer. A browser might also offer additional measures in this area; for example, if Firefox's "Resist Fingerprinting" setting is enabled, many media queries report default values rather than values representing the actual device state. -## Formal syntax - -{{csssyntax}} - ## Examples ### Testing for print and screen media types From a9280d06d6e78ec8fc35d3a7a0f7f98d921370e0 Mon Sep 17 00:00:00 2001 From: Sean <34548230+srcengine@users.noreply.github.com> Date: Sat, 28 Dec 2024 11:26:39 -0800 Subject: [PATCH 012/265] Update example to clarify the sum of flex-grow factors (#37359) * Update index.md Try to clarify and solidify example and summations... Specifically, differentiate between the number of grow-factors vs. the sum of the grow-factors. Please review. * Apply suggestions from code review --------- Co-authored-by: Estelle Weyl Co-authored-by: Estelle Weyl --- files/en-us/web/css/flex-grow/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/files/en-us/web/css/flex-grow/index.md b/files/en-us/web/css/flex-grow/index.md index 33b42c95612bf51..4d3a46764d2e282 100644 --- a/files/en-us/web/css/flex-grow/index.md +++ b/files/en-us/web/css/flex-grow/index.md @@ -45,7 +45,7 @@ The remaining space, or positive free space, is the size of the flex container m If the `flex-grow` values differ, the positive free space is distributed according to the ratio defined by the different flex grow factors. The `flex-grow` factor values of all the sibling flex items are added together. The flex container's positive free space, if any, is then divided by that total. The main size of each flex item with a `flex-grow` value greater than `0` will grow by this quotient multiplied by its own growth factor. -For example, if four `100px` flex items are in a `700px` container and the flex items have `flex-grow` factors of `0`, `1`, `2`, and `3`, respectively, the total main size of the four items is `400px`, meaning there is `300px` of positive free space to be distributed. There are a total of 6 grow factors (`0 + 1 + 2 + 3`). Therefore, each grow factor is equal to `50px` (`(300px / 6 )`. Each flex item is given an amount of positive free space equal to this amount multiplied by its `flex-grow` value — so `0`, `50px`, `100px`, and `150px` respectively. The total flex item sizes are, therefore, `100px`, `150px`, `200px`, and `250px`, respectively. +For example, if four `100px` flex items are in a `700px` container and the flex items have `flex-grow` factors of `0`, `1`, `2`, and `3`, respectively, the total main size of the four items is `400px`, meaning there is `300px` of positive free space to be distributed. The sum of the four grow factors (`0 + 1 + 2 + 3 = 6`) is equal to six. Therefore, each grow factor is equal to `50px` (`(300px / 6 )`. Each flex item is given 50px of free space multiplied by its `flex-grow` factor — so `0`, `50px`, `100px`, and `150px` respectively. The total flex item sizes become `100px`, `150px`, `200px`, and `250px`, respectively. `flex-grow` is generally used alongside the other {{cssxref("flex")}} shorthand properties, {{cssxref("flex-shrink")}} and {{cssxref("flex-basis")}}. Using the `flex` shorthand property is recommended to ensure all values are set. @@ -61,7 +61,7 @@ For example, if four `100px` flex items are in a `700px` container and the flex ### Setting flex item grow factor -In this example, there is a total of eight growth factors distributed among the six flex items, meaning each growth factor is `12.5%` of the remaining space. +In this example, the sum of six flex-grow factors is equal to eight, meaning each growth-factor value is `12.5%` of the remaining space. #### HTML From 93dbdf2aa1a8cb90497b3256b57c14d73200b0f3 Mon Sep 17 00:00:00 2001 From: Snuggs <38223+snuggs@users.noreply.github.com> Date: Sat, 28 Dec 2024 14:37:56 -0500 Subject: [PATCH 013/265] Fix invalid markup in index.md (#37409) * Fix invalid markup in index.md There was an orphan `` & `

` when there should have been a closing `` * linter * Update files/en-us/web/accessibility/aria/attributes/aria-valuenow/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --------- Co-authored-by: Estelle Weyl Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- .../accessibility/aria/attributes/aria-valuenow/index.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/files/en-us/web/accessibility/aria/attributes/aria-valuenow/index.md b/files/en-us/web/accessibility/aria/attributes/aria-valuenow/index.md index aab9d21454c80dc..7c8469cf80ce081 100644 --- a/files/en-us/web/accessibility/aria/attributes/aria-valuenow/index.md +++ b/files/en-us/web/accessibility/aria/attributes/aria-valuenow/index.md @@ -74,12 +74,8 @@ When the value to be announced, either the actual value or the value as a percen The first rule of ARIA use is "if you can use a native feature with the semantics and behavior you require already built in, instead of repurposing an element and **adding** an ARIA role, state or property to make it accessible, then do so." ```html -