CSS1 Test Suite Results: NGLayout Engine
This page lists results of running NGLayout through the W3C's CSS Test
Suite, and a few other tests. However, I also have a number
of my own tests, for which the results are not listed
here.
Status of This List
- Last run through whole suite for new bugs: Build of 1998 December 19.
- Last run through existing bugs to see if they still exist: Build of 1998 December 19, with slight modifications 1999 February 03.
Previous Versions of this page
Bugs from Test Suite
The list that follows is a list of bugs in the browser, that is,
what is described is in error. I sometimes only mention the bug the
first time it occurs in the test suite. I have also included a few
partially supported features as bugs because, although it would be
acceptable to completely fail to support the feature, supporting it
halfway can cause unexpected results.
- 1.1
- Alternate stylesheet interface is primitive.
- 1.3
- The underlining is ugly. It does not have a stable baseline
(though it does have solid color), which it should, since
text-decoration is not inherited, but, rather, spans children.
(See Bug 1019)
(See Bug 1777)
- 2.5
- Pseudo elements are incorrectly allowed at places other than the end of
the simple selector.
(See Bug 2000 - this is now fixed)
(See Bug 2011 - this is now fixed)
- 4.1.1
-
-
Nested margins do not collapse (.six .five .seven) properly.
(See Bug 1378)
-
The non-floating paragraph is way too low (.eleven). It should not
be moved by any floating elements.
(See Bug 1279)
- 4.1.2
-
The left border is one pixel too thin on its left edge. (Note: the
pixel ruler has an extra pixel *and* starts with zero, so it acts like
the first pixel is -1.
(See Bug 1052)
- 4.1.4
-
In the first DIV, the floats are not high enough.
(See Bug 2013)
-
There is extra space between the first and second lines of text in the second DIV.
(See Bug 1279)
-
In the fifth test, the top of a float cannot be higher than the top of
a previous float.
(See Bug 2013)
-
In the sixth test (non-DIV), the floater is not high enough.
(See Bug 1279)
- 4.2,
5.5.11b,
5.5.12b,
5.5.13b,
5.5.14b,
5.5.15b,
5.5.16b,
5.5.17b,
5.5.18b,
5.5.20b,
5.5.22b
- The text of the inline elements should not change baseline when a border
starts.
- The ends of the borders are ugly. They shouldn't have diagonal edges.
(See Bug 2010)
- Margins on the top and bottom of inline elements shouldn't do anything.
- Borders of inline elements should not increase the line-height.
- Borders on inline elements should not change the baseline.
(See Bug 1606)
(See Bug 1508)
- 4.4
-
The page is a mess!!! The old list of bugs is:
-
I don't think (???) the 3px half-leading is appearing before the new
lines properly.
-
The images with border and margins should be aligned based on their
outer edges, not content edges.
-
I'm not sure the last image is quite right.
(See Bug 2014)
- 4.5
-
The BODY margin-top gets the color of BODY.
(See Bug 1580)
(See Bug 2016 - should be fixed)
- 5.2.2
-
This page is a real mess. Cursive, fantasy, and monospace don't do
what they should in the first part, but monospace somehow becomes
better when there is an alternative font-family after it. Fonts in
the DIV seem to be changing the size of fonts within - in the second
DIV, with the monospace font. There may be some other weird things
too. This is explained in bug 582.
(See Bug 1038)
(See Bug 581)
(See Bug 582)
- 5.2.5
- Judging from MSIE5, you could do a little better with the weight
900 (which also applies to the
H4
with bolder
.
(See Bug 972)
- 5.2.6
- Negative values should not be allowed.
(See Bug 1039 - should be fixed now)
- 5.2.7,
5.4.8
- Line heights in ems, percentages, and scaling factors look like
they might be based on the original line-height rather than the
font-size. However, it's hard to tell.
(See Bug 585)
- Backgrounds of inline elements should not fill the line-height. The line height should also be split between both sides of the text.
(See Bug 585)
- 5.2.7
-
The BODY font size does not inherit correctly into the TABLE.
(See Bug 1044)
- 5.4.3
-
text-decoration
should span children with text-decoration
set to none (including images).
(See Bug 1019)
(See Bug 1777)
- 5.4.5
-
- There is no capital letter after
.
- Accented letters are not text-transformed.
(See Bug 2015)
- 5.5.01b,
5.5.03b,
5.5.05b
-
Top and bottom margins on inline elements should not do anything, because
they do not increase the line spacing.
(See Bug 1606)
(See Bug 1508)
- 5.5.04
-
When the page is narrowed, the TABLE won't shrink past a certain
point. This may be OK. If it is maximized from a narrowed position
then display problems result.
(See Bug 2022)
- 5.5.06,
5.5.06b,
5.5.07,
5.5.07b,
5.5.08,
5.5.08b,
5.5.09,
5.5.09b,
5.5.10,
5.5.10b
-
Negative padding values are not allowed (in both CSS1 and CSS2). They
have messy effects here.
(See Bug 2012 - should be fixed now)
- 5.5.06b,
5.5.08b,
5.5.10b
- Top and bottom padding on inline elements should not
increase the line spacing and should not mess up the baseline alignment.
(See Bug 1606)
(See Bug 1508)
- 5.5.13b,
5.5.15b,
5.5.22
- 5.5.13b: The thin border on the inline element is thinner inside the table.
- 5.5.15b: The border is thinner on the bottom and the right outside the table and
thinner on the right inside the table.
- 5.5.22: The thin maroon border is thinner on the bottom and the double one varies by side.
(See Bug 1052)
- 5.5.15
- The top border is 1px (?) thinner than the rest. This is
especially visible on thin.
(See Bug 591)
(See Bug 1052)
- 5.5.17
-
Cosmetic bug: some of the borders (dotted, dashed especially) could use some work.
(See Bug 1054)
- 5.5.18,
5.5.19
5.5.20
5.5.21
5.5.22
- (Old version of suite (for tests 18 and 20 only): The
thin
(top & bottom) border is thinner inside
the table.) Now it is gone.
(See Bug 1055)
- 5.5.25
- The first
P
inside the table doesn't have its usual
margin-top.
(See Bug 1583)
- 5.5.25b
-
-
The image being moved up and left 30 pixels is being moved right 60
pixels instead of left 30 pixels.
(See Bug 1605)
-
The image with a positive bottom margin is causing weird effects --
this should be fixed if the margins on inline elements bug is
fixed. Also, the text in the third paragraph starts too low.
(See Bug 1508)
(See Bug 1606)
- 5.5.25c
-
-
The image in the second paragraph should end up after the paragraph since
there is no room for it.
(See Bug 2025)
-
In the sixth test, the paragraph background should not overwrite the
background of the float
(See Bug 1277)
-
Floats within tables have problems. The table, for some reason, is
way too wide.
(See Bug 1059)
-
The
CLEAR="ALL"
isn't quite doing the trick. The HR
after the seventh test gets shortened. CSS Clear isn't working on
later pages (5.5.25d, etc.)
(See Bug 1808)
- 5.5.25d
-
-
There is a horizontal line running across the image that shouldn't
be there.
(See Bug 2024)
-
Also (see above), the image isn't cleared.
(See Bug 1808)
- 5.5.26
-
The top margin of the
P
element isn't applied to the first
element inside the table.
(See Bug 1583)
- 5.5.26b
-
This page is messy, but I think all the bugs are dealt with earlier,
except that the yellow DIV is a little bit low.
Add bugs here??
- 5.5.26c
- Overconstrained box properties on BODY don't set margin-right to auto.
(See Bug 1300)
- 5.6.5
list-style-position:
is set in ua.css
on
an LI
, so the test doesn't work.
(See Bug 1049)
- 7.1
-
-
//
is not a valid CSS comment and should result in errors.
(See Bug 1812 - this is now fixed)
-
The following bugs are related to section 7.1, but are not part of the test page itself (see my unitless numbers test):
border-width: 200;
is inacceptable and should be rejected.
border-width: 200 px;
is inacceptable and should be rejected.
border-top-width: 200 px;
is inacceptable and should be rejected.
Unsupported Features from Test Suite
A: visited
, A: active
(2.1) - A
and A:link are supported - the distinction is made correctly.
(See Bug 577)
(See Bug 1848)
background-attachment:
(5.3.5)
(See Bug 1045)
Other Tests
My own test pages
See the results page for my tests to see how
NGLayout does overall. However, for those tests marked as buggy (B),
the bug numbers are:
For the curious (i.e., me)
(Back to
CSS Testing Information,
David Baron)
LDB,
dbaron@dbaron.org