User Interface for CSS3

Hello,

I have some points to consider about the User Interface for CSS3 
Workin Draft:


System colors:

Why are there no DefaultButton and DefaultButtonText systemcolors?
I see no reason to make an exception here.

I myself have been using a slighlty lighter background and text color
for the default buttons in my web applications, it gives the interface
more elegance.

It's also much easier and nicer to implement.
It gives:

[<empty>|enabled|disabled|active|hover]
 x [the 14 UI elements]
 x [<empty>|Text|Border]

(5x14x3=210)


The 'key-equivalent' property:

It would be very usefull for the 'key-equivalent' property
if you would define default system key equivalents.

Example:
INPUT.ok { key-equivalent: return enter Y }

I am Dutch speaking, so I would expect an J for Ja instead of a Y for Yes.
So 
INPUT.ok { key-equivalent: systemOK }
would be a more general solution.

I also do not know what the expected macintosh keys are. With default
system key equivalents, I don't have to know them.


the 'user-select' property:

toggle and all are effectively the same:
If one selects something with user-select set to all, everything will be
selected.
If the user then selects it again, everything will be deselected again.
So this is completely the same as toggle.
The only difference is the expected look, which is set through all the
different kinds of other CSS properties.


the 'user-focus' property:

Are all combinations of the 'user-focus' property and the 'user-select'
property possible? (there sure are a lot of combinations that 
make sense, most of the user-focus values seem to apply only 
on the user-select:text property)


I must say this proposal makes a very nice combination with the new XHTML
form ideas. It would be even nicer if eventually every (XML) element could
be made input-enabled on the fly. (makes it very easy to write an editor)


Sjoerd Visscher
Locosoft bv

Received on Friday, 17 September 1999 17:12:07 UTC