[css-env-1][editorial] Add media queries to meta text-scale explainer

Author: davidsgrogan

css-env-1/explainers/meta-text-scale.md

@@ -143,6 +143,33 @@ That means:
 
 We expect `scale` to become best practice for authors to use on all new website designs, just as they use the viewport meta tag. It allows authors to continue to use font-relative units like `rem` and `em` like they normally would and mostly avoid using `env(preferred-text-scale)`.
 
+> [!NOTE]
+> It has been pointed out that these two approaches
+> **currently behave identically** on mobile,
+> though there is a theoretical difference in the specification:
+>
+> **1. The Meta Tag Approach**
+> ```html
+> <meta name="text-scale" content="scale" />
+> ```
+>
+> **2. The CSS Approach**
+> ```css
+> :root {
+>   font-size: calc(env(preferred-text-size) * 16px);
+>   text-size-adjust: none;
+> }
+> ```
+>
+> **Theoretical Difference:**
+> * **With `<meta>`:** (r)em-based media queries **will include** the OS-level font setting.
+> * **With `:root`:** (r)em-based media queries **will NOT include** the OS-level font setting.
+>
+> *The difference is theoretical because the `env` spec says
+> [`env()` works in media queries](https://drafts.csswg.org/css-env-1/#valdef-env-preferred-text-scale:~:text=Because%20environment%20variables%20don%E2%80%99t%20depend%20on%20the%20value),
+> but no browser supports that as of 2025.
+> Consequently, there is no difference.*
+
 ### Comparison of `legacy` and `scale`
 
 This comparison table summarises our proposal. **`legacy`** describes current behavior. **`scale`** represents a simple way for sites to obey the OS-level text settings.