- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 05 Mar 2026 16:18:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-forms-1] Specify readonly input styles`, and agreed to the following: * `RESOLVED: close this issue no change, can revisit if needed` <details><summary>The full IRC log of that discussion</summary> <jarhar> lwarlow: currently theres no handling of the readonly state in the css forms spec<br> <jarhar> lwarlow: if people could think about what readonly should look like<br> <jarhar> lwarlow: perhaps they should just look like standard controls, perhaps like disabled<br> <jarhar> lwarlow: we just need to come to a consensus. if it applies in both cases, then we will add a note to the spec that this is deliberate<br> <jarhar> astearns: for this case, do you have an impression of whether its important that the user styling controls would allow you to achieve the various kinds of styling that we get in the different browsers?<br> <jarhar> lwarlow: basic css can achieve both of those, theres nothing special we need to introduce<br> <jarhar> lwarlow: we just need to decide on styles and think about the behavior of things<br> <jarhar> smaug: does this depend on the operating system? does something happen on macos vs windows?<br> <jarhar> lwarlow: readonly is a weird one since it doesnt apply to various inputs<br> <masonf> the HTML readonly attribute is ignored if the type is hidden, range, color, checkbox, radio, file, submit, reset, button, and image<br> <jarhar> lwarlow: i know it doesnt apply to select and a few other things, so theres weirdness around that side of things as well<br> <jarhar> lwarlow: i dont know that we want to change which ones it applies to. leaving it as-is is probably ok<br> <jarhar> annevk: whether it can be readonly seems like an html question. we should just decide how its going to be styles. whether its focusable or not, thats more of an os parity question<br> <jarhar> masonf: it probably shouldnt change that list - readonly doesnt change whether its focusable. its an a11y question, right? you want to focus it and see that its readonly??<br> <jarhar> annevk: also the focus outline is up to the ua so that we dont have to consider either for any other things<br> <jarhar> annevk: and the text caret, i dont know<br> <jarhar> annevk: is styling of text carets a thing? i think thats also up to the browser<br> <jarhar> lwarlow: you can change the color and animation<br> <jarhar> lwarlow: chrome also has caret shape<br> <astearns> https://drafts.csswg.org/css-ui-4/#the-insertion-caret<br> <jarhar> annevk: that should work but whether it shows in a readonly control or not, that doesnt seem like ... its an interesting question but out of scope<br> <jarhar> masonf: you said in the issue that chromium renders a text caret on windows, i just tried on mac and it doesnt<br> <jarhar> lwarlow: no i tried on mac<br> <jarhar> zcorpan: the mouse cursor turns into an i beam if you hover, but when you click theres no caret<br> <jarhar> masonf: the i beam is because you can still select/highlight<br> <jarhar> masonf: im in favor of leaving it as is because the behavior becomes clear when you try to type in it, you dont get a caret<br> <jarhar> lwarlow: im happy to resolve on that<br> <jarhar> lwarlow: we can revisit and come back to this if theres cases where browsers disagree<br> <jarhar> astearns: resolving then to close this issue no change?<br> <jarhar> lwarlow: yes<br> <jarhar> lwarlow: i might add a note to the spec, but normatively no change<br> <jarhar> masonf: css forms has no styling for the readonly state? then yeah i agree<br> <jarhar> proposed resolution: close this issue no change, can revisit if needed<br> <jarhar> RESOLVED: close this issue no change, can revisit if needed<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12490#issuecomment-4006229408 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 March 2026 16:18:49 UTC