Re: [csswg-drafts] [css-forms-1] Use visibility for checkmark control? (#13226)

The CSS Working Group just discussed `[css-forms-1] Use visibility for checkmark control?`, and agreed to the following:

* `RESOLVED: keep checkmark as content value in checked state, use visibility to hide`

<details><summary>The full IRC log of that discussion</summary>
&lt;lwarlow> q+<br>
&lt;bramus> fantasai: the current set of style is changing the content property of the checkmark, so we are destroying and recrating it when checked/unchecked. In most cases you dont want a different symbol instead of destorying it. so we should probably use content-visibility for it<br>
&lt;astearns> ack lwarlow<br>
&lt;bramus> lwarlow: +1 to that, but wha tabout interminite? I think they dont match :checked<br>
&lt;bramus> … so setting content on ??<br>
&lt;bramus> … therem ay be a case for checkmarks on switches. for all these reasons using content-vsibiliyt makes sense<br>
&lt;bramus> fantasai: so we would set visibiility;hidden when the checkbox is neither checked nor indeterminte<br>
&lt;masonf> q+<br>
&lt;bramus> masonf: probably very small compat issue but sounds trivial, so i’m in favor<br>
&lt;bramus> lwarlow: this is specificically for ??? but for select we already do this<br>
&lt;bramus> masonf: ok, thanks<br>
&lt;bramus> astearns: so proposed resolution is to not change the content property but use content-visibility<br>
&lt;bramus> fantasai: and when it’s unchecked, it would continue to have a checkmark in the content<br>
&lt;fantasai> RESOLVED: keep checkmark as content value in checked state, use visibility to hide<br>
&lt;fantasai> s/checked/unchecked/<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13226#issuecomment-3921714093 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 18 February 2026 16:10:26 UTC