Do you switch between display: block and display: none frequently?
Isn't it a chore having to retype absolute and relative to change between position values?
When you don't remember all the acceptable values of, say, white-space, isn't it a bother having to google that again and again?
That's where the keyword previewer comes in.
When the user sets the caret on a CSS value keyword, e.g. inline-block, a previewer pops up with the rest of the available values for the specific property.
To change the value, just click on the value you want.
I've already done some preliminary work on this, and found it'd be easier to implement if the tokenizer recognised CSS keywords. But I don't know if Lea would be interested in such a feature.
Do you switch between
display: block
anddisplay: none
frequently? Isn't it a chore having to retypeabsolute
andrelative
to change between position values? When you don't remember all the acceptable values of, say,white-space
, isn't it a bother having to google that again and again?That's where the keyword previewer comes in. When the user sets the caret on a CSS value keyword, e.g.
inline-block
, a previewer pops up with the rest of the available values for the specific property. To change the value, just click on the value you want.I've already done some preliminary work on this, and found it'd be easier to implement if the tokenizer recognised CSS keywords. But I don't know if Lea would be interested in such a feature.