CKTIS / CSS
appearance — native, primitive, and compatibility rendering of widgets
`appearance` chooses whether a form widget keeps its platform-native rendering or exposes a primitive/base appearance that ordinary CSS can paint.
Version: CSS modules; structured CSSWG indexes reconciled with pinned MDN BCD; Chromium 152 scope gate, per-example verification still required
Syntax
none | auto | base | base-select | <compat-auto> | <compat-special>appearance chooses whether a form widget keeps its platform-native rendering or exposes a primitive/base appearance that ordinary CSS can paint.
Three checked checkbox controls remain semantically checked (true/true/true). Native auto measures 13x13; unprefixed none becomes a custom 24x18 red box (rgb(220, 0, 0)), and -webkit-appearance with none becomes a 26x20 blue box (rgb(0, 80, 220)).
Grammar: none | auto | base | base-select | <compat-auto> | <compat-special>.
none suppresses native widget appearance without removing control semantics, while auto lets the host language and UA choose the native widget. CSS UI 4 is a Working Draft; base and base-select describe emerging interoperable base appearances, but the draft explicitly says base is not ready to ship until HTML defines the stylesheet. Compatibility groups <compat-auto> and <compat-special> preserve selected historical keywords. The required -webkit-appearance spelling is a legacy-name alias of appearance; that compatibility requirement does not make every old prefixed value interoperable. Prefer the unprefixed property, retain the alias only for tested legacy targets, and restore focus and state cues when removing native paint.
Examples
document.body.innerHTML =
'<style>input{margin:0}.plain{appearance:auto}.standard{appearance:none;width:24px;height:18px;background:rgb(220,0,0)}.legacy{-webkit-appearance:none;width:26px;height:20px;background:rgb(0,80,220)}</style>' +
'<input class="plain" type="checkbox" checked><input class="standard" type="checkbox" checked><input class="legacy" type="checkbox" checked>';
const controls=[...document.querySelectorAll('input')];
await new Promise(requestAnimationFrame);
const describe=element=>{const style=getComputedStyle(element),box=element.getBoundingClientRect();return style.appearance+'/'+Math.round(box.width)+'x'+Math.round(box.height)+'/'+style.backgroundColor;};
console.log('native='+describe(controls[0])+'; standard='+describe(controls[1])+'; prefixed='+describe(controls[2])+'; checked='+controls.map(control=>control.checked).join('/'));Result
native=auto/13x13/rgba(0, 0, 0, 0); standard=none/24x18/rgb(220, 0, 0); prefixed=none/26x20/rgb(0, 80, 220); checked=true/true/true
`appearance` chooses whether a form widget keeps its platform-native rendering or exposes a primitive/base appearance that ordinary CSS can paint.