CSS1 Test Suite Results: NGLayout Engine
Status of This List
- Last run through whole suite for new bugs: Build of 1998 November 17 (preliminary copy of new version of test suite).
- Last run through existing bugs to see if they still exist: Build of 1998 December 10.
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.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)
- 4.1.1
- Nested margins do not collapse (.six .five .seven) properly.
- The non-floating paragraph is way too low (.eleven). It should not
be moved by any floating elements.
- Width on floating elements does not work in tables.
- 4.1.4
- In the first DIV, the floats are not high enough.
- In the third, fourth, fifth DIVs, the text does not begin at the top.
- In the sixth test (non-DIV), the floater is not high enough, and it overlaps the margin of the next test because
clear does not work quite right.
- There are very serious problems within the TABLE, mainly with width assignment.
- 4.2,
5.5.11b,
5.5.12b,
5.5.13b,
5.5.14b,
5.5.15b,
5.5.16b,
5.5.17b,
etc.
- Inline element borders are a mess
- The ends of the borders are ugly. They shouldn't have diagonal edges.
- Margins on the top and bottom of inline elements shouldn't do anything.
- Borders of inline elements should not increase the line-height.
(See Bug 1606) - ADD TO THIS BUG- 4.3
- The resizing seems to be turning a square into a rectangle.
- 4.4
- 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.
- 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)
- 5.2.7,
5.4.8
- Most line-heights seem to be a little big. I think they are being done
relative to the default rather than to 1. However, it's hard to tell.
(See Bug 585)
- 5.2.7
- The BODY font size does not inherit correctly into the TABLE.
- 5.4.3
- text-decoration should span children with text-decoration set to none.
- 5.4.5
- There is no capital letter after
.
- Accented letters are not text-transformed.
- 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. I'm not sure.
- 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.
- 5.5.04
- When the page is narrowed, the TABLE won't shrink past a certain point. This may be OK.
- 5.5.06b,
5.5.08b,
5.5.10b
- Top and bottom padding on inline elements should not
increase the line spacing.
- 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.20
- (Old version of suite: The
thin (top & bottom) border is thinner inside
the table.) Now it is gone. (This applies to tests 19 and 21 and 22 as well.)
(See Bug 1055)
- 5.5.25
- The vertical alignment of the floats is correct, but the paragraphs
flowing around them are pushed down too far. I have a modified version
of this page where it is incorrect, along with other
bugs. See the CSS2
Specs.
- 5.5.25b
- The image being moved up and left 30 pixels is being moved right 60
pixels instead of left 30 pixels. Also, the image with a positive bottom
margin is causing weird effects -- this should be fixed if the margins on
inline elements bug is fixed.
(See Bug 1605)
(See Bug 1606)
- 5.5.25c
- Floats with a width as a percentage were not resized when the
window is resized.
(See Bug 1060)
- The image in the second paragraph should end up after the paragraph.
- In the fifth example, the paragraph should flow under the drop cap
on the third line. The drop cap ends up a little too low and with too
much padding, which may prevent this. It has too much top and bottom
margin or padding.
- In the test .five, the paragraph background should not overwrite the
background of the float
(See Bug 1277 - UPDATE THIS BUG)
- Floats within tables are a mess. (A huge mess!)
(See Bug 1059)
- The
CLEAR="ALL" isn't quite doing the trick. CSS Clear isn't working on later pages (5.5.25d, etc.)
(See Bug 1808 - UPDATE THIS BUG)
- 5.5.25d
- There is a horizontal line running across the image that shouldn't be
there.
- 5.5.26
- The text should be higher... it should not be pushed down by the
existence of the floats.
- 5.5.26b
- The yellow rectangle is moved down by the clear on the previous float.
Elements in the normal flow should not be affected.
- 5.5.26c
- This test is a mess. I'm not going to describe all the problems in
detail. The font isn't inheriting into the table, and some of the
floats are moved down too far (although we can argue over spec wording
versus intention here).
- 5.6.1
list-item doesn't work anymore. Could this have
something to do with bullet placement? This should start working when
inside works, because then the bullet will be in the
paragraph (this isn't quite true, and actually it shouldn't be).- 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)- The declaration for P.twentytwo trips up the parser, but it shouldn't. It should end up green.
- 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
- Alternate Stylesheets (1.1)
A: visited, A: active
(2.1) - A
and A:link are supported - the distinction is made correctly.
(See Bug 577)background-attachment:
(5.3.5)
(See Bug 1045)
Other Tests
(Back to
CSS Testing Information,
David Baron)
LDB,
dbaron@dbaron.org