From a891b4d32527f5598e20fe33023aa662d372e712 Mon Sep 17 00:00:00 2001 From: Stephanie Zhang Date: Mon, 8 Dec 2025 14:27:48 -0800 Subject: [PATCH 1/5] initial changes --- FormControlRange/explainer.md | 193 ++++++++++++++-------------------- 1 file changed, 77 insertions(+), 116 deletions(-) diff --git a/FormControlRange/explainer.md b/FormControlRange/explainer.md index 6aea7dea9..c821f3fc5 100644 --- a/FormControlRange/explainer.md +++ b/FormControlRange/explainer.md @@ -1,4 +1,4 @@ -# FormControlRange +# OpaqueRange ## Authors: @@ -10,14 +10,17 @@ - [WHATWG tracking issue](https://github.com/whatwg/html/issues/11478) - [CSSWG issue tracking initial discussions](https://github.com/w3c/csswg-drafts/issues/10346) +- [TPAC 2025 WHATWG Meeting Minutes](https://www.w3.org/2025/11/11-whatwg-minutes.html) - [TPAC 2024 WHATWG meeting minutes on initial proposal](https://github.com/whatwg/meta/issues/326#issuecomment-2377500295) -- [Issue tracker](https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/FormControlRange) +- [Issue tracker](https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/OpaqueRange) ## Introduction The current `Range` interface methods do not support retrieving or creating ranges that represent the `value` (rather than the element itself) of `