- From: Kevin Babbitt via GitHub <noreply@w3.org>
- Date: Wed, 05 Nov 2025 22:28:04 +0000
- To: public-css-archive@w3.org
@emilio > * We probably need the border-width resolved value to account for border-style. Do you agree with that intuition? Yes I agree; part of the resolution was that we'd leave resolved value of border-width unchanged. > * It seems Chromium hasn't quite implemented this right? At least, with this resolution, tests like [`border-width-011.xht`](https://wpt.fyi/results/css/CSS2/borders/border-width-011.xht) should fail. What exactly did you implement? Tagging @oSamDavis since he did the implementation to correct me if I'm wrong, but as I understand: * Behavioral changes are behind the Experimental Web Platform Features flag. * Computed values of border-width, outline-width, and column-rule-width are changed per the resolution. * Resolved values of outline-width and column-rule-width (but not border-width) are changed per the resolution. * We have use counters in place to measure potential breakage, though I don't know if they've been in long enough to give us useful data yet. -- GitHub Notification of comment by kbabbitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11494#issuecomment-3493851282 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 November 2025 22:28:04 UTC