Css With Firefox

[khalilov 0]

Warning: Unknown property 'scrollbar-face-color'.  Declaration dropped.Source File: http://localhost/game/mainpage.cssLine: 8Warning: Unknown property 'scrollbar-highlight-color'.  Declaration dropped.Source File: http://localhost/game/mainpage.cssLine: 9Warning: Unknown property 'scrollbar-3dlight-color'.  Declaration dropped.Source File: http://localhost/game/mainpage.cssLine: 10Warning: Unknown property 'scrollbar-darkshadow-color'.  Declaration dropped.Source File: http://localhost/game/mainpage.cssLine: 11Warning: Unknown property 'scrollbar-shadow-color'.  Declaration dropped.Source File: http://localhost/game/mainpage.cssLine: 12Warning: Unknown property 'scrollbar-arrow-color'.  Declaration dropped.Source File: http://localhost/game/mainpage.cssLine: 13Warning: Unknown property 'scrollbar-track-color'.  Declaration dropped.Source File: http://localhost/game/mainpage.cssLine: 14

for some reason these don't work with firefox, i have 3.0

[Mordent 0]

Hmmm, you're right. They don't work with Firefox 3.0 (pass as to 2.x, I haven't got it any more). IE seems to handle the CSS fine (I checked both browsers using W3Schools), which does make me wonder...

 

Looking at the list of CSS properties (found here) I can't see anything do with the scrollbar on there. Perhaps it's something that IE supports that isn't a standard? It wouldn't surprise me, what with IE's stance on general web standards ("those things people keep mentioning? Yeah, we might look at them sometime when we're done doing stuff we want to do...").

[FirefoxRocks 0]

The scrollbar properties are currently IE only properties. They are not part of the CSS 2.1 standard. I'm not sure if there are scrollbar properties defined within the CSS3 specification (it's a bit hard to navigate). I think that web designers should NOT have the ability to alter the colours of the scrollbar because it is a component of the user interface, not the page itself. For example, by changing the theme of GNOME/Linux, the scrollbar, window borders, etc all change colour. Same goes for Windows for Windows programs that are developed with the Windows "windows" (notable exceptions include iTunes and Safari).

[pyost 0]

This is something that only IE supports (though there could be other browsers as well), but those properties don't follow W3C standards - in other words, those properties don't even exist. While Firefox is well known for it's proper CSS rendering and following standards, this is not something IE can brag about. Not to mention that a lot of people are not keen on their scrollbar changing colour

[Animator 0]

It really slacks me off when they slip in their own extras like that. It's what made a mess of HTML before when IE was versus Netscape, resulting in a tonne of tags, all variations of the same effect. When CSS was introduced, one of the biggest pulls of it was to set common standards so all web browsers would experience the same page within reason of backwards compatibility. While scrollbar colour isn't going to upset browsers in the backwards-compatable sense, it still shows Microsoft trying to edge ahead in sneaky ways again.

[wutske 0]

It really slacks me off when they slip in their own extras like that. It's what made a mess of HTML before when IE was versus Netscape, resulting in a tonne of tags, all variations of the same effect. When CSS was introduced, one of the biggest pulls of it was to set common standards so all web browsers would experience the same page within reason of backwards compatibility. While scrollbar colour isn't going to upset browsers in the backwards-compatable sense, it still shows Microsoft trying to edge ahead in sneaky ways again.

It's true that it messes things up, but this way new CSS properties are introduced. A lot of things we can do with CSS nowadays were probably not possible if nobody added new properties to their browsers. Also, nobody forces you to use this browser-specific properties, simply follow the CSS guidelines and use properties that every browser understands and everything should be okay. The only problem you might have is that some browsers interpret properties in a different way ... then you have to create a small script that loads those properties differently for that browser. It sucks, but there's nothing we can do about it