CSS is so cool. So cool. But not in terms of UI for a CSS editor...
- let's suppose you can have your text 'bold' or 'normal'; one checkbox or checkboxButton is enough, and you can have this button live with other buttons like italic, underline and others
- let's suppose now you can have your text 'bold', 'normal or
unspecified ; a few options here:
- one checkbox to say the boldness is specified or not and a checkbox/checkboxButton for bold
- two checkboxes/checkboxButtons for 'bold' and 'normal'; property is unspecified when both are unchecked
- a menulist with three choices
- let's suppose now, and that's the CSS real case that matters to me,
boldness can take the values 'bold', 'normal', 'bolder', 'lighter',
'inherit', 'initial', 100, 200, 300, 400, 500, 600, 700, 800, 900 or can
be unspecified... The two reasonable choices here are:
- one checkbox to say the boldness is specified or not and a menulist
- a menulist where 'unspecified' is one of the options
In other terms, offering the full power of the 'font-weight' CSS property to a CSS editor will necessarily suck in terms of UI (yeah, forcing a menulist when most users will only use the 'bold' choice just sucks)... I am even tempted to have two modes in the CSS editor, basic and advanced. Pffff....