- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Fri, 19 Sep 2025 12:12:27 +0000
- To: public-css-archive@w3.org
@ziransun Sorry for the slow answer, I had not seen your question. But thanks for asking. This is indeed fairly subtle to test, because the spec deliberately gives implementations flexibility to do things differently. Your tests seem reasonable *for chromium*, but they're not fully generic/cross-browser. Neither were mine, to be fair, and for the same reason: we are both assuming a particular placement/shape of the caret, but since that's implementation dependent, the tests are not cross browser. I think what we should do instead is to use negative ref-tests. The point is that the caret should be visible *somehow*. Exactly where it goes and what it looks like may vary, but something should be visible. So I think the best solution is to make a reference file where there is no caret visible, and then to use [`rel="mismatch"`](https://web-platform-tests.org/writing-tests/reftests.html#components-of-a-reftest) from the tests to check that the rendering is different from that. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10289#issuecomment-3311959551 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 September 2025 12:12:27 UTC