- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Nov 2023 18:19:02 +0000
- To: public-css-archive@w3.org
I am concerned by this assertion in [`t32-opacity-clamping-0.0-b.xht`](https://github.com/web-platform-tests/wpt/blob/master/css/css-color/t32-opacity-clamping-0.0-b.xht) by @dbaron (which [all browsers pass](https://wpt.fyi/results/css/css-color/t32-opacity-clamping-0.0-b.xht?label=master&label=experimental&aligned&q=opacity)): ```html <meta name="assert" content="Opacity values less than 0.0 are clamped to 0.0" /> ``` and similarly in [`t32-opacity-clamping-1.0-b.xht`](https://github.com/web-platform-tests/wpt/blob/master/css/css-color/t32-opacity-clamping-1.0-b.xht) which again [all browsers pass](https://wpt.fyi/results/css/css-color/t32-opacity-clamping-1.0-b.xht?label=master&label=experimental&aligned&q=opacity): ```html <meta name="assert" content="Opacity values greater than 1.0 are clamped to 1.0" /> ``` So **specified** values are _not_ clamped (see [codepen](https://codepen.io/lilles/pen/YzjQEzj by @lilles) but **computed** values (which is what @dbaron was testing) _are_. Right? -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8311#issuecomment-1830427873 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 November 2023 18:19:03 UTC