 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion GroupsGeneralPHPASPPerlColdFusionFlashHTML, CSS, ScriptsBrowsers |
Webmaster Forum / HTML, CSS, Scripts / CSS / August 2007How come CSS system colors have been depricated ?
Hello I am just writting a custom JavaScript control for one of my web pages and it is gread to write controls that look just like the native ones. How come system colors have been depricated in CSS 3 ? Why limited systems that have no system colors could not just supply some constant default values like white for all system background colors and black for all system text and borders colors ? Thank you, Timothy Madden, Romania Scripsit Timothy Madden: > I am just writting a custom JavaScript control for one of my web pages > and it is gread to write controls that look just like the native ones. I'm pretty sure that this is true for some interesting meanings for the word "gread". I think you just coined a new cool word into the English language! > How come system colors have been depricated in CSS 3 ? Nothing has happened to them yet. CSS 3 is just a collection of drafts of varying status, generally progressing slowly in some development track, if any. Did you check the archives of the work on CSS 3 Colors to find out why people doing that work plan to remove or deprecate system colors? > Why limited systems that have no system colors could not just supply > some constant default values like white for all system background > colors and black for all system text and borders colors ? Well, that wouldn't be a problem. But if you ask me, there are few if any good use cases for system colors. You might use them in instruction manuals for some software, when describing its user interface, assumed to vary by system and its settings. This is however a rather specialized case. Writing custom controls for a web page tends to be counter-productive. The controls won't be the same as the normal controls, and making then look similar to them would generally confuse rather than help. I'm not saying that you should never have page-specific or site-specific controls on web pages. I'm saying that they should look _different_ from the controls that are part of the browser's or operating system's normal interface, to avoid confusion. If a page contains a Print button, it should definitely look different from a browser's Print button  SignatureJukka K. Korpela ("Yucca") http://www.cs.tut.fi/~jkorpela/ I did not check the CSS3 archives yet. CSS 2.1 is in production now and it says 'System colors are depricated in CSS3 Color Module' This is not good. I have two multi-select lists in my page where visitors can transfer options from one list to another and back. Now my client tells me he wants the options grouped, in both lists, and the wants to be able to transfer groups as well as options. This is why I need my own control, that would work just like a SELECT element with OPTGROUPs in it, but would let me select option groups also. I could also use a plain SELECT control and format some of the options in bold, and indent the others, but MSIE does not support this. So why should my clients see something different just to be able to select groups of options as well as options ? Timothy Madden, Romania > Scripsit Timothy Madden: > [...] [quoted text clipped - 27 lines] > interface, to avoid confusion. If a page contains a Print button, it > should definitely look different from a browser's Print button I did not check the CSS3 archives yet. CSS 2.1 is in production now and it says 'System colors are depricated in CSS3 Color Module' This is not good. I have two multi-select lists in my page where visitors can transfer options from one list to another and back. Now my client tells me he wants the options grouped, in both lists, and the wants to be able to transfer groups as well as options. This is why I need my own control, that would work just like a SELECT element with OPTGROUPs in it, but would let me select option groups also. I could also use a plain SELECT control and format some of the options in bold, and indent the others, but MSIE does not support this. So why should my clients see something different just to be able to select groups of options as well as options ? Timothy Madden, Romania > Scripsit Timothy Madden: > [...] [quoted text clipped - 27 lines] > interface, to avoid confusion. If a page contains a Print button, it > should definitely look different from a browser's Print button > I'm not saying that you should never have page-specific or site-specific > controls on web pages. I'm saying that they should look _different_ from > the controls that are part of the browser's or operating system's normal > interface, to avoid confusion. I disagree. Buttons should look like the users' operating system so that their function (i.e as a button) is clear. Why should the user have to learn all _your_ interface elements as well as the OS? An excellent example of this is the funky scroll controls that Flash developers like to inflict on us that never _quite_ work the way you expect. Steve. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.