CSS1TS Errata: First Draft

A list of changes proposed for the CSS1 Test Suite, and the current planned resolution of each proposal.

Resolutions in bold red text are still under consideration. Resolutions in black and backed in pale yellow are assumed to be definitively resolved, unless a major objections is raised. A lack of any resolution, proposed or otherwise, is an open invitation to make suggestions.

SectionCommentsResolution
ALL

The DOCTYPE should be HTML 4.0 Strict instead of HTML 4.0 Transitional.

Not felt to be sufficiently important to change everything.
ALL

One suggestion: it would be easier to use if the output lines were numbered. This would make it much quicker to match the code with the corresponding output.

This may happen on a few of the long tests, but will not be implemented for all pages. (Already a planned feature for the CSS2 Test Suite.)
VARIOUS

There are identical IDs in the same document, thanks to the table-testing replication. For example:

I think there is a HTML error in section 4.1.2 [1] in the CSS1 Test Suite (and possibly other sections as well) : The complete test is repeated twice on the page (once by itself, and once inside a table). The problem is that there is a paragraph with an id in the test, which means that there is two paragraphs with the same id (<P ID="ruled"> on lines 76 and 146).
I would very much appreciate if this could be fixed, since my CSS application (which I naturally want to test against the Test Suite) is unforgiving to invalid HTML (which I consider a feature), and hence can't be tested against the current version of the Test Suite.

See also test pages for sections 1.3, 1.5, 2.1, 3.1, 3.2, and 5.5.25.

Alter documents which suffer from this problem to have differing IDs for each section.
BORDERS

Do borders apply to table cells and rows, let alone TABLE elements? If not, the border tests are in serious error.

They do, so no changes are necessary.
BORDERS

Also, the inline border tests are hard to see since both the inline and block-level borders are black. I propose changing the block-level to gray, or something similarly contrasting with the inline border colors.

Change paragraph border to be gray.
1.0

The previous page is not "sec03.htm", but "sec04.htm".

Fix link.
1.5

I would like to change the text to say something like:

"This sentence should be black, not red-- ID selectors cannot begin with digits in CSS1. Note that CSS2 doesn't have this restriction and this sentence should be red with CSS2-compliant browsers."
Remove test altogether, as it tests HTML compliance instead of CSS compliance.
2.1
  1. I think that "for the A element" is better than "for the A tag".
  2. "It also should NOT turn orange" should read "turn maroon".
Make indicated changes.
2.4

On the "2.4 first-letter" test page, the third example states "...should by 350% bigger than the rest of the paragraph...". This may be incorrect, since the specification implies that the percentage is taken from the normal font size (where 100% is the same size as the normal font). Suggested corrections (unless I am wrong):

"...350% THE FONT SIZE of the rest of the paragraph..."
"...250% bigger than the rest of the paragraph..."

It's late, and I may not be making sense. But I think this, despite being a common practised "feature" of our language, misleads those who intend to use the suite. When I first read it, I thought, "that W isn't 350% percent bigger, it's only about 250% percent bigger!".

Change text to read "...should be 3.5 times bigger than the rest of the paragraph..."
2.5

I think that "The first line of this paragraph, and only ..." is better than "The first line of this sentence sould be ...", because the last two paragraph have more than one sentence.

Make indicated changes.
3.1
  1. I think that all "This sentence ..." should read "This paragraph".
  2. In the paragraph id1, I think that "than the declarations which have ID selectors" is better than "given in a STYLE attribute".
Make indicated changes.
4.1.2
  1. In the sixth paragraph, I think that "the left margin" is better than "the margins that are set to ...".
  2. In the seventh paragraph, I think that "the right margin" is better than "the margins that are set to ...".
(This refers to the first two of the three 100%-wide paragraphs just after the 50%-wide auto-left paragraph.)
Make indicated changes (the tests are now somewhat vague, and this would make them more clear). Also make similar changes for the third of the three paragraphs.
4.3

In the fourth and fifth paragraph, "and the table in the second" sould read "in the table cell in the second".

Make indicated changes.
4.3

The "fifty pixel square" is not intrinsically fifty pixels tall or wide-- the size is actually 15x15. Should we change the wording, or the image?

Change the wording, not the image.
5.3.2

"SPANned word 'sentence' " sould read "SPANned word 'background' ".

Make indicated changes.
5.3.5

This page does not test for the "alignment" of fixed backgrounds on child elements with the fixed background of ancestor elements (including BODY/HTML). Should this be added here, or should it wait for the CSS2 test suite?

Put it off to CSS2 Test Suite.
5.5.09b
This element is unstyled save for a background color of gray. However, it contains an inline element of class two which should result in -10px left padding (which should also be a light blue) only in the first line in which the inline box appears. http://www.w3.org/Style/CSS/Test/current/sec5509b.htm

As Tapio from Finland just pointed out to me and David, padding cannot take negative values! As far as I can tell, the other padding pages do not have this error. I do not know how this page has escaped the careful error pruning of a few months back...

Make indicated changes.
5.5.17b

In section 5.5.17 the style shows correctly but it is described incorrectly. Class 2 should be red (and shows that way) but the text says it should be purple.

Change style to use purple, and leave text alone.
5.5.26

I feel the sec5526.htm is not enough for 'clear' test. To check 'clear'ing tallest float element on one side, I think there must be some float images in various height on both sides.

Leave the test alone.
5.6.4

The images run together, making it hard to see what's happening. Change image to circle or other visually discontinuous shape.

Change images to circles.
7.1

There is an example ("P.two") whose text states:

"This paragraph should have a solid gray background (or a white grid), because in CSS1, inherit is an invalid keyword, and in CSS2, it will cause the gray background (not the white grid) to be inherited."

The applicable rule is:

 P.two {background-color: inherit;}

This statement correct for the first occurrence of this statement, where the parent of the P is the BODY which has background-color: #CCCCCC, and therefore is inherited to the P in CSS2.

However, the second occurrence of this statement is in a P inside a TD, and the TD has no background-color specified (therefore gets the initial value of "transparent"), and therefore the P's inherit value inherits "transparent" in CSS2, and therefore the white grid of BODY shows through.

A slight rewording of the descriptive text would fix "P.two":

"This paragraph should have a solid gray background (or a white grid), because in CSS1, inherit is an invalid keyword, and in CSS2, it will cause the gray background (not the white grid) to be inherited in the first part of the document, and a transparent background (thus allowing the white grid background of BODY to shine through) to be inherited in the second part of the document when inside the TD."
Change text to describe results under both CSS1 and CSS2, taking each in turn.