The @w3c MathML Core specification, now at #CandidateRecommendation status, defines a core subset of the #MathML 3 specification designed for reliable, interoperable web browser support. It focuses on mathematical notation rendering, tightly integrating with #HTML, #CSS, and DOM standards to ensure consistency, testability, and minimal implementation complexity. #timetoimplement
▶️ https://www.w3.org/TR/mathml-core/

Feedback welcome: https://github.com/w3c/mathml-core/issues/

Explainer: https://github.com/w3c/mathml-core/blob/main/docs/explainer.md

@w3c has released "Pointer Events Level 3" as #CandidateRecommendation #timetoimplement
▶️ https://www.w3.org/TR/pointerevents3/

This specification aims to simplify development across diverse input devices like mouse, pen, and touchscreens. Along with expanded #CSS touch-action values, new features include altitudeAngle and azimuthAngle properties for detailed stylus input.

Feedback welcome: https://github.com/w3c/pointerevents/

Pointer Events

The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen. For compatibility with existing mouse-based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.

The @w3c Compute Pressure #API specification defines a set of pressure states (e.g. high CPU load) delivered to a #WebApp to signal when adaptation of the workload is appropriate to ensure consistent quality of service. #timetoimplement
▶️ https://www.w3.org/TR/compute-pressure/

The document defines 3 concepts: processing units (such as the CPU), supported sources (such as #GPU), sampling and reporting rates.

Key usage scenarios are described in this explainer: https://github.com/w3c/compute-pressure#readme

Compute Pressure Level 1

The Compute Pressure API provides a way for websites to react to changes in the CPU pressure of the target device, such that websites can trade off resources for an improved user experience.

The @w3c Timed Text #WorkingGroup invites implementations of the "Dubbing and Audio Description Profiles of TTML2 (DAPT)" specification for exchanging timed text content in #dubbing and #audio description workflows #timetoimplement

▶️ https://www.w3.org/TR/dapt/

DAPT enables scripting, voicing, and mixing for dubbing and audio descriptions, supporting video #localization and #accessibility.

Feedback welcome in https://github.com/w3c/dapt/

Dubbing and Audio description Profiles of TTML2

@w3c invites implementations of Controlled Identifiers (CIDs) v1.0

CIDs generalizes the mechanism used to prove control of an identifier in Decentralized Identifiers (#DID), making it also applicable to non-decentralized identifiers and systems (e.g. HTTPS URLs). They can be used with Verifiable Credentials, e.g. to authenticate the subject of such a credential
#timetoimplement
▶️ https://www.w3.org/TR/cid-1.0/

Bring input and feedback on the #GitHub repo: https://github.com/w3c/cid/

Controlled Identifiers v1.0

A controlled identifier document contains cryptographic material and lists service endpoints for the purposes of verifying cryptographic proofs from, and interacting with, the controller of an identifier.

WebGPU Shading Language (WGSL), the shader language for WebGPU, also reached the @w3c #CandidateRecommendation status
▶️ https://www.w3.org/TR/WGSL/
#timetoimplement

Shaders are the most important when it comes to rendering in WebGPU. WebGPU Shading Language) lets #developers write shaders for draw commands in the render pipeline and dispatch commands in the compute pipeline exposed by #WebGPU.

Feeback welcome: https://github.com/gpuweb/gpuweb/issues/

WebGPU Shading Language

Better, faster and easier to use!

The @w3c WebGPU #API lets developers use high-performance GPU computing and advanced rendering, offering faster operations and modern GPU support as #WebGL's successor #timetoimplement
▶️ https://www.w3.org/TR/webgpu/

WebGPU opens up new programming possibilities in #browsers.
Check #WebGPU samples and demos: https://webgpu.github.io/webgpu-samples/

Feedback welcome: https://github.com/gpuweb/gpuweb/issues

WebGPU

The @w3c #WebAssembly Core Specification is now a #CandidateRecommendation
▶️ https://www.w3.org/TR/wasm-core-2/
#timetoimplement

This doc. outlines release 2.0 of the core WebAssembly standard, a secure, portable, low-level code format. The update improves #performance, including support for SIMD (Single Instruction Multiple Data) to enhance #parallel processing on compatible #CPUs.

Check which #WASM features are supported across #browsers in
https://webassembly.org/features/

Feedback: https://github.com/WebAssembly/spec/issues

WebAssembly Core Specification

The newly published @w3c #CandidateRecommendation "Device Posture API" allows #WebApps to request and be notified of changes of the posture of a device #timetoimplement
https://www.w3.org/TR/device-posture/

Device posture refers to its physical position, detected via sensors. With foldable devices, understanding posture is key for responsive design, especially when the device isn’t fully flat.

Read the explainer: https://github.com/w3c/device-posture/blob/gh-pages/README.md
Feedback welcome: https://github.com/w3c/device-posture/

Device Posture API

This document specifies an API that allows web applications to request and be notified of changes of the posture of a device.

📣 Call for implementations for the W3C Baggage specification which defines a #HTTP header to propagate contextual information as part of a distributed request to enable better observability or better control of the system. #timetoimplement
▶️ https://www.w3.org/TR/2024/CR-baggage-20240530/

Baggage works independently of Trace Context and can be used without Distributed Tracing.

▶️ See also the explainer: https://github.com/w3c/baggage/tree/main/baggage

Comments are welcome in #GitHub: https://github.com/w3c/baggage/

Propagation format for distributed context: Baggage

This specification defines a standard for representing and propagating a set of application-defined properties associated with a distributed request or workflow execution.