scrollbar color codes

[kimmie]

Hi,

I'm new to this forum stuff and actually new to dealing with web page design. I'm using Frontpage 2003 to create a webpage. I found the codes needed to change the color of the scrollbar. The problem is that it is the wrong color and I would like for the entire bar to be colored. What are the codes for the following colors: dark green, yellow, and a light green? Also how do I get a two colored bar? Thanks for your help.

[Twey]

HTML colours are composed of a hash (#), then three sets of two hexadecimal digits representing red, green and blue light. Yellow is composed of red and green, so the yellowest yellow you can make is #ffff00 (full red, full green, no blue). Green is composed only of (surprise) green light, so the brightest green is #00ff00 (no red, full green, no blue). For a darker green, use less blue; try #007f00, for instance (no red, half green, no blue). Also, in place of HTML colours, standard colour names can be used; "green," for example, will give you a darkish green, while "yellow" and "lime" will give you the light yellow and green colours, respectively.

Using FrontPage is a bad idea. WYSIWYG editors in general tend to mangle anything that's put through them, and FrontPage is reputed to be the worst of the lot. I suggest you create your pages yourself.
Also, the CSS properties used to change the colour of the scrollbar are proprietary IE-only. They only work in IE, and will make your page invalid. Therefore, they aren't really worth using; there are schools of thought that say you shouldn't use them even if such downsides did not exist.
Regarding valid code: run your page through a validator. This isn't a total assurance of quality, but it's certainly a step.

[kimmie]

Twey, thanks for the help. I ran it through the validator and it showed up 26 errors. What type of program do you recommend for creating web pages?

[robertcathles]

Sorry to interrupt, I was just browsing through.

Using FrontPage is a bad idea. WYSIWYG editors in general tend to mangle anything that's put through them, and FrontPage is reputed to be the worst of the lot.

I have happened to use FrontPage in my own website coding and it seems to work perfectly fine. One problem I found before was that I was saving some pages in Microsoft Word 2002. In Word, when I went Save As Web Page, it came up with some of the most horrible code I have ever seen. There were "mso-" tags everywhere. However, when I used FrontPage, it made my code really simple and much easier to organise.

Personally, I wouldn't suggest something like Macromedia DreamWeaver and a template page. I have used this software before, and it is really good - but costs a great amount for my liking. However, one of my friends imported copied code from another HTML-based website, and after about a month's worth of editing, the code was starting to rip the page apart.

Nevertheless, I have found a really useful free WYSIWYG editor called ASP.NET Web Matrix. It works quite well and can do lots of different formats, although I only use HTML!

kimmie, if you want some more Hexadecimals, here are some links:

• http://symantec.com/avcenter/hex.color.codes.html
• http://msdn.microsoft.com/library/de...ors/colors.asp - includes all the hexadecimals for all the colours with names
• http://www.trafficzap.com/colorpicker.php - don't think this one is working anymore
• http://www.fontstuff.com/frontpage/namedcolors.htm
• http://resources.bravenet.com/quickref/color_codes/

Also, the CSS properties used to change the colour of the scrollbar are proprietary IE-only

Yes, it's a bit of a pain in the neck, that one, isn't it? Ahh, the wonders of Internet Explorer. But also: Ahh, the wonders of Mozilla Firefox.

[Twey]

I have happened to use FrontPage in my own website coding and it seems to work perfectly fine.

I hate WYSIWYG editors in general personally, but FrontPage specifically only through reputation. I'm not surprised at the mess a word processor would make of a webpage, though.

Yes, it's a bit of a pain in the neck, that one, isn't it? Ahh, the wonders of Internet Explorer.

If Microsoft want to add daft features, they should bring them before the W3C, of which they are a part. I suspect the rest of the committee would have rejected this one, though.