scrollbars

If you use a newer DOCTYPE you have to apply the styles to the HTML element as well as BODY, so use
html, body { style: stuff here; }
For your selector.

Also, scrollbar colouring is not recognised across all browsers. In fact, if I remember correctly, it is an IE-only feature.

thanks guys

@nm: Works in Opera. Dunno about Firebird.

Let me get this straight. To accomodate a proprietary extension in one browser; we (who are ostensibly open source supporters) are now abandoning the recommendations for css to which all the browser vendors are signatories by changing the DOC TYPE supplied. I did hear correctly? If one of the major benefits of using WP is valid XHTML output is it worth chucking it away?

“We” are not abandoning anything. This is a personal choice from one user.
Don’t get your panties in a bunch.

@anonymous:
If I chose to use tables and loads of them on my Blog. Does that reflect the choice of the WP community in general? My Blog does not validate either. Ban me guys, I am polluting the air around WP.

Why would people who don’t care about validation use WordPress? I’m just interested, because I always got the impression that standards compliance was THE main thing that brought people to this tool. If your priority is weird colored scrollbars you might as well stick to Blogspot.

I don’t like google.
I don’t like Blogger.
I could not install MT.
I did not try any other tool.
I am happily using WordPress; for my Blog. As my journal.
Not as a tool to show how good I am at XHTML/CSS which incidently I am not.
Never knew, Making a Validating site was a pre-requisite of using WP.
My priority is my Blog, not the tool I use.

I guess my question should really be – why wouldn’t you think producing valid code that complies with standards is important? The developers have gone to the trouble of making code that validates, so why butcher it with weird IE-specific stuff? If something’s worth doing it’s worth doing properly.

1. scroll bars are not IE only afaik.
2. not only IE specific tag breaks the validation, small things like <br> too does that.
and i believe if it works for me, and it’s not a site for the generic public so as to speak (it’s a journal for god sake!), it works for me. But ok i agree. don’t embarrass the effort by making ultra ugly crappy site that works on nothing but the makers own browser and monitor. ??

Thank u Allusion, ur answer is the best!

@sushubh – <br> breaks validation because it is not valid. Empty elements should have a closing slash included like so:
.

I think it’s inevitable that if you post a question to do with scrollbar colors in any kind of css forum there are going to be responses from a variety of stand points.
I do not think it is unkind to suggest that a lot of folk here are plainly very new to css. Issues about validation may be very personal. They do however form part of any well informed response to the posted question. I am with WillM on this.
As usual. ??

Well, in my case, the reason I picked WP was because: 1) it was easy to use (including install and getting started) and 2) Written in PHP, which I know how to program in (as opposed to Perl, which I don’t know at all). The fact that it is semantiaclly correct is just a bonus. I have “problems” with that sometimes, but I see the benefit of having it so. At the same time, being open source, there’s nothing in the way of hacking the core to get it to produce different output than it normaly does. Does that make it wrong or any less right? No. It just makes it different. I don’t claim to know alot about CSS, but I know a lot more now than I did 6 months ago when I started working with WP.
Just like with anything else, there is a learning curve. Jsut depends on how much time you want to invest.
TG