Yichun Wang wrote:
> sorry, I mean I just have met many problems. Take a example, in IE5.0,
> the css attributes like vertical-align, margin, border, there have no
> effects when applied to the inline elements, and in Mozilla(I use
> 0.8.1, have the gecko changed much now?), this attributes are
> supported.
Note that in IE5.5 and later, these properties are also supported on
inline elements. It's a matter of Microsoft implementing standards very
late in the game. Also, with each release they "fix" some of their
properties which were previously implemented but implemented wrong. For
an example, the CSS1 box model in IE5.5 and earlier was wrong (it
included border and padding in the width) but in IE6 it has been fixed
(but only when you use a standards-compliant doctype.) This irks me to
no end as a web developer; I've already had to drop IE from my support
matrix for internal projects because there is no guarantee of
forwards-compatibility. If they had just waited and implemented the
standards right the first time around instead of getting greedy and
implementing them wrong and having to "fix" them later, the web would be
a much better place. This is why I greatly appreciate Mozilla's approach
of strictly honoring standards and getting it right the first time
around (for the most part). I just wish all web developers would realize
this.
I would strongly recommend you upgrade from Moz 0.8.1 -- So much has
improved, particularly performance. Also, Netscape 6.1 is based on Moz
0.9.2, so upgrading would allow you to get closer to what Netscape users
are seeing.
> So I am wondering about how the Mozilla makes the decisions
> to support CSS1.0 or higher, and in what level it supports them?
I'm not sure there is really a decision-making process for this, besides
weighing the difficulty and risk of implementing a property. The
published idea is to implement all of CSS1 and spotty CSS2. Some CSS3
properties are also being implemented, but with the -moz- prefix so
there is no future confusion. Also, the Moz developers have implemented
all properties/selectors that are necessary for styling the browser's
interface and widgets. This includes many proprietary properties, but
they all have the -moz- prefix.
> Another problem is when the pages are not well-formed, two browsers
> act with little in same.
>
Why is this an issue? Your documents should *always* be well-formed.
Mozilla makes an effort to handle common mistakes gracefully, but
that's no excuse for current authors to create shoddy code.
--J
