CSS1 Test Suite Results: NGLayout Engine

Status of This List

• Last run through whole suite for new bugs: Build of 1998 September 2.
• Last run through existing bugs to see if they still exist: Build of 1998 October 08.

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

Not a "bug": The underlining is ugly. (See Bug 1019)

5.2.2

This page is the first 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. (See Bug 1038) (See Bug 581)

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

• medium is not equivalent to the default font size. This is a serious (and common) bug. Therefore, the whole scaling of all the relative font sizes is off. The definitions of relative font sizes should be changed, and BODY {font-size: medium} should go in ua.css. (See Bug 973)
• The font sizes in ex are way too small. This is also very serious. (See Bug 974)
• Negative values should not be allowed. (See Bug 1039)

5.4.3

Underlining does not stay constant color as (?) it should. (See Bug 1019)

5.4.4

middle (See Bug 606) and text-bottom (I think) and 50% aligns are done incorrectly. The reflow with image loading acts a bit oddly as well. (See Bug 1040)

5.5.01, 5.5.02, 5.5.03, 5.5.04, 5.5.05

The *-margin: 25% doesn't shrink enough when the page is narrowed (reflow problem?). (That is, it stops shrinking when the page is narrowed beyond a certain point.) (See Bug 1041)

5.5.05

The elements with width: 50% are not centered by the auto settings in the left and right margin. (See Bug 1042)

5.5.06, 5.5.08, 5.5.09, 5.5.10

The percentage units on padding are way to small, as they should be based on the parent element's width. They are sometimes even zero. (See Bug 853, which says this may be fixed on date of 10-8 build)

5.5.11, 5.5.12, 5.5.13, 5.5.14 5.5.15

• An element with border-style:none but a declared border width gains extra padding because of the border-width. (The browser correctly shows no border.) (See Bug 1050 - this should be fixed in the 10-9 build)
• The top border also seems to be 1px thinner than the rest. This is especially visible on thin. (See Bug 591) (See Bug 1052)

5.5.16

The setting of border-style should be enough to create a border. The default border-width is medium. (This could go in ua.css on *, if you support * .) (See Bug 1051 - reported as fixed on 1998-October-12)

5.5.17

• groove and ridge are reversed, if you want to be consistent with the upper-left lighting model, which is standard, and which is used in inset and outset. (See Bug 1053)
• Cosmetic bug: some of the borders (dotted, dashed, inset, outset especially) could use some work. (See Bug 1054)

5.5.18, 5.5.20

The thin (top & bottom) border is thinner inside the table. (See Bug 1055)

5.5.25

The vertical alignment of the floats is technically correct, but may not be the best choice. However, I have a modified version of this page where it is incorrect, according to CSS2, along with other bugs. See the CSS2 Specs.

5.5.25b

• The text should appear on top of the fifth image, not be hidden by it. (I think.)
• Floats should not move above their containing block-level element. When they do, the margins of that block level element are calculated as if the float were in the right place. (Wait: does this apply to negative margins??)
• Should a paragraph be moved down if it has a floating element within it with a negative top margin????

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, which may prevent this. It has too much top and bottom margin or padding.
• Reflow is very slow. (See Bug 1059)
• Floats within tables are a mess. (A huge mess!) (See Bug 1059)

5.5.26

clear: is not supported. I consider this a bug, since float: is supported (although not completely working...). However, it appears that the following paragraphs are being affected by the clear. (See Bug 707)

6.1

ex units are way too small. (See Bug 974)

6.2

• The 25% left margin loads incorrectly on inital load if the window has been resized since NGLayout started. However, it is correct on reflow. (See Bug 1058)
• The margins do not apply properly when outside of the table. (See Bug 1057)

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)
• :first-letter (2.3) (See Bug 578)
• :first-line (2.4) (See Bug 579)
• font-variant: small-caps (5.2.4) (See Bug 584)
• background-position:, except that it seems to affect the width of the background images in 5.3.7. I have seen it cause two rows of background images on other pages too. (5.3.4, 6, 7) (See Bug 1045)
• background-attachment: (5.3.5) (See Bug 1045)
• word-spacing: (5.4.1) (See Bug 1046)
• letter-spacing: (5.4.2) (See Bug 1046)
• text-transform: (5.4.5) (See Bug 587)
• text-align: justify (5.4.6) (See Bug 1047)
• text-indent: (5.4.7) (See Bug 1048)
• line-height: (5.2.7, 5.4.8) (See Bug 585)
• list-style-position: (5.6.5) (See Bug 1049)

(Back to CSS Testing Information, David Baron)

LDB, dbaron@dbaron.org