Welcome!

[rd_online]

Hi there!
The topic CSS was already posted for version 3; but what about a matrix showing the differences/opportunities for CSS 1/2/3 and (e.g.) the 3 most common browsers?

We had many articles about png-errors, different interpretation of tags etc etc etc...what do you think about this approach to shorten the coding part so that this lovely book won´t just be another programming handbook?

[Furmi]

Hi rd_online

Well, the related post on CSS 3 is here to point the differences out. In our days, you won't need CSS 1, at least you're before-IE 5.5 browsers coding. CSS 2 is the common language since, and is well interpreted by common browsers (except IE, as always, with padding bugs etc.).

So, CSS 3 topic will be to point the update out, towards CSS 2.

However, explain all the differences between them three will turn into a programming book, for sure.

[GeoEgo]

I can't see this as being very useful. There's little to no reason to use CSS 1 at this point, and CSS 3 isn't even near being complete.

[rd_online]

Hi GeoEgo and Furmi,
thanks for your critics, but I won´t let get away that fast : )

- Since you both considered the time-issue (old browser-versions with outdated css), lets crop it to CSS 2/2.1/3 and browsers > IE6 or similar
-

However, explain all the differences between them three will turn into a programming book, for sure.

Rightee in this one, too....but isn´t that always the case? This way we can at least ensure that the book will not be a view to the past but also in the future....

[GeoEgo]

Hi GeoEgo and Furmi,
thanks for your critics, but I won´t let get away that fast : )

- Since you both considered the time-issue (old browser-versions with outdated css), lets crop it to CSS 2/2.1/3 and browsers > IE6 or similar

I still can't see it. We can't cross-reference CSS3 and the current browser versions, being as the CSS3 standard is so far from complete. Having said that, I think there's validity in discussing CSS issues with modern browsers, but more in context than a dedicated article.

However, explain all the differences between them three will turn into a programming book, for sure.

Rightee in this one, too....but isn´t that always the case? This way we can at least ensure that the book will not be a view to the past but also in the future....

I'm all for looking at the future, but not so far that it's pure speculation, which is basically what CSS3 is at this point. The only aspect that's any further than a candidate recommendation is the SVG portion, meaning that everything else is entirely subject to change. This doesn't make me feel too warm and fuzzy about committing any of the information to print.