Frames maybe dropped before being sent to the encoder for various reasons（source、congestion、rate limit), stats dropped frames for every dropped reseaon may be more complicated, i think this(capture fps -> webrtc input fps -> encoder fps) is acceptable.

deploy: 97f676cf01d22614e5a69abee27cb831f70f4ebc

Apply automatic changes

fix eval headings

Merge pull request #13 from w3c/shawna-slh-patch-3

fix eval headings

Note: This issue title includes "directly-related terms" to keep this issue going on tangents. In scope of this issue is the terminology quoted below, including "auditory". Feel free to open separate issues for other terms.

WAI resources such as Introduction to Web Accessibility and How People with Disabilities use the Web - draft revision use the following categories of disabilities or impairments:

auditory, cognitive and learning, neurological, physical, speech, visual

WCAG 2 includes:

Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

Adam Cooper brought up an issue with "visual disabilities|impairments" versus "vision disabilities|impairments" in an e-mail to wai-eo-editors that includes:

The word 'visual' is about what is seen as in 'visual art'. The word 'vision' is about seeing rather than what is seen as in 'envisioning'. to say something is 'visually impaired', therefore, is tantamount to saying the appearance of that thing is itself impaired. The phrase 'vision impairment' rather than 'visually impaired' or 'visual disability' is used by the World Health Organisation in the International Classification framework of Functioning, Disability, and Health, and by the U.N. more broadly.

(and Kevin chimed in with a story and:

I tend to use 'sight impaired' now.

Please add to this issue input — especially authoritative references — to inform the possibility of WAI changing terminology from "visual disability|impairment" to "vision disability|impairment" (or "sight disability|impairment").

Update agenda.html

Update agenda.html

@chrisn I'm also unconvinced about this change. Setting aside whether there was consensus in the PATCG, I did say i'd open this issue on the template for discussion. I'm surprised to see it merged.

Update support.html

Update agenda.html

Update agenda.html

Update agenda.html

Update agenda.html

Update of TR report from new reffy run

Using reffy commit 13.0.3.

This is a tracker issue. Only discuss things here if they are i18n group internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ https://github.com/w3c/csswg-drafts/issues/8442

Instructions (delete this line and all following):

• check for the following labels, then remove the PENDING label, then delete these instructions

• Check that TRACKER & S:... labels are there

• Add t:... label(s) to indicate the topic (same as ids in specdev)

• If urgent add:

• add ADVICE-REQUESTED label if the WG-issue is specifically asking for i18n to advise/comment

• add NEEDS-ATTENTION label if this is an important issue

• if there's an i18n-*lreq label in the WG repo check for:

  • ...LREQ label(s) there should be one or more
  • SPEC-TYPE-ISSUE label (dark green background) should be there
  • TYPE-INFO-REQUEST label (red background) if this is a WG-issue that constitutes a request for script/language expert advice
  • i:... label(s) to indicate the Language Enablement Index category

This is a tracker issue. Only discuss things here if they are i18n group internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ https://github.com/w3c/csswg-drafts/issues/8554

Instructions (delete this line and all following):

• check for the following labels, then remove the PENDING label, then delete these instructions

• Check that TRACKER & S:... labels are there

• Add t:... label(s) to indicate the topic (same as ids in specdev)

• If urgent add:

• add ADVICE-REQUESTED label if the WG-issue is specifically asking for i18n to advise/comment

• add NEEDS-ATTENTION label if this is an important issue

• if there's an i18n-*lreq label in the WG repo check for:

  • ...LREQ label(s) there should be one or more
  • SPEC-TYPE-ISSUE label (dark green background) should be there
  • TYPE-INFO-REQUEST label (red background) if this is a WG-issue that constitutes a request for script/language expert advice
  • i:... label(s) to indicate the Language Enablement Index category

Update data

Update agenda.html

Update agenda.html

⚠ NEVER add commits to this pull request.

🤖 This pull request was automatically created to facilitate human review of @webref/idl changes triggered by curated data at 4f6f1743a277e10cbb78e9c5648457200b7e54cb.

🧐 Please review the diff below and version numbers. If all looks good, merge this pull request to release the changes to npm.

📦 Latest released @webref/idl package was v3.34.3. Merging this pull request will release v3.34.4. Make sure that the bump is the right one for the changes.

✍ If any change needs to be made before release, do not add a commit to this pull request. Changes should rather be handled in a separate pull request and pushed to the main branch. You may leave this pull request open in the meantime, or close it. The pre-release job will automatically update this pull request or create a new one once the updates have made their way to the main branch.

🛈 The actual change introduced by this pull request is a version bump in packages/idl/package.json. You do not need to review that change. The bumped version is not the version that will be released when this pull request is merged, but rather the version that will be released next time.

diff --ignore-trailing-space '--exclude=package.json' '--exclude=README.md' '--exclude=CHANGELOG.md' '--unified=3' webref/node_modules/@webref/idl/scroll-animations.idl packages/idl/scroll-animations.idl
--- webref/node_modules/@webref/idl/scroll-animations.idl
+++ packages/idl/scroll-animations.idl
@@ -6,8 +6,8 @@
 enum ScrollAxis {
   "block",
   "inline",
-  "horizontal",
-  "vertical"
+  "x",
+  "y"
 };
 
 dictionary ScrollTimelineOptions {

diff --ignore-trailing-space '--exclude=package.json' '--exclude=README.md' '--exclude=CHANGELOG.md' '--unified=3' webref/node_modules/@webref/idl/webgpu.idl packages/idl/webgpu.idl
--- webref/node_modules/@webref/idl/webgpu.idl
+++ packages/idl/webgpu.idl
@@ -604,7 +604,7 @@
 
 [Exposed=(Window, DedicatedWorker), SecureContext, Serializable]
 interface GPUPipelineError : DOMException {
-    constructor((DOMString or undefined) message, GPUPipelineErrorInit options);
+    constructor(optional DOMString message = "", GPUPipelineErrorInit options);
     readonly attribute GPUPipelineErrorReason reason;
 };

Bump @webref/idl version from 3.34.4 to 3.34.5

Update of ED report from new reffy run

Using reffy commit 13.0.3.

Bump @webref/elements version from 2.2.2 to 2.2.3