- From: Luke Warlow via GitHub <noreply@w3.org>
- Date: Mon, 13 Apr 2026 20:57:51 +0000
- To: public-css-archive@w3.org
For future reference the extra logs that got cut off at the beginning of the logs above are (taken from bottom of https://github.com/whatwg/html/issues/11819#issuecomment-3468618193) ``` <noamr> lwarlow: css forms. the way it is currently spec'ed is if your originating element has a value the pseudo-element gets it as well. seemingly makes sense <noamr> lwarlow: this is strange sometimes because e.g. a button can get appearance: none by mistake <jarhar> q+ <noamr> lwarlow: currently you can (inconsistently) mix and match, e.g. appearance: auto element with none pseudop-element <noamr> lwarlow: happy to say "stop doing that". will chromium/webkit be open to it? <noamr> emilio: in particular with form controls like checkboxes/meter etc. it doesn't make sense to have appearance:none inside appearance:auto or vice versa <noamr> lwarlow: browsers, for some reason, give file input appearance:none <noamr> zcorpan: file input uses css layout but then has a button inside with appearance:none. IIRC that's what we specified <noamr> zcorpan: we can change the UA stylesheet but not sure it solves anything <dbaron> github: https://github.com/https://github.com/whatwg/html/issues/11819 ``` -- GitHub Notification of comment by lukewarlow Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12931#issuecomment-4239583842 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 April 2026 20:57:52 UTC