Mozilla now supports all CSS1 properties

EmilEifrem writes "Looks like the Mozilla team's doing good: "The new layout engine now supports all CSS1 properties. Troy Chevalier implemented the last property, background-attachment, earlier this week. Some properties are still buggy, and one selector (the visited pseudo-class) isn't yet implemented. However, this is probably the most complete implementation of CSS1 so far, and the bug list is consistently getting shorter." Check story at MozillaZine. "

Comments

Re:Mozilla a failure?

[davie]

Personally, I think JWZ's departure and subsequent comments were all about sour grapes. I didn't expect mozilla to be "hacker friendly" for at least a year, I don't understand why anyone would have. Granted, the project has a bit of a "family atmosphere," but what else should we expect?

In hindsight, dumping the legacy rendering engine will probably be seen as the salvation of mozilla. It's smaller, faster and easier to maintain, at least according to the comments I've read from developers. After the code stabilizes we'll probably see gecko popping up in all kinds of applications and a lot more interest in development. I think mozilla is going to put the screws to Internet Exploder and will eventually become the de facto standard against which other browsers are measured.

Re:Argh! Drop CSSn and get it out

[Masem]

I don't think so. First, here's a quote from
w3's page:

Will XSL replace CSS?

No. They are likely to co-exist since they meet different needs. XSL is intended for complex
formatting where the content of the document might be displayed in multiple places; for
example the text of a heading might also appear in a dynamically generated table of contents.
CSS is intended for dynamic formatting of online documents for multiple media; its strictly
declarative nature limits its capabilities but also makes it efficient and easy to generate and
modify in the content-generation workflow. So they are two different tools; for some tasks,
CSS is the appropriate choice and for some tasks, XSL. They can also be used together - use
XSL on the server to condense or customize some XML data into a simpler XML document, then
use CSS to style it on the client.

Secondly, most average web authors will for the next 2 to 3 years will still be using HTML for
most pages, and CSS is the only way to format
these types of pages.

However, the apparent problem with CSS is that it
has been standardized by the W3 group for several
years, and only *now* are we seeing fully compatible browsers, mostly due to the trail ends
of the browser wars. It's a shame that there
is all this tech in web content delievery that
an author cannot take advantage of because
of incomplete browsers.