CSS Test Suite Results: Opera 3.51 for Windows 32-bit

Previous Versions of This Page

• 3.50 beta 9 1998-??-??
• 3.50 beta 10 - 1998-11-06
• 3.50 beta 11 - 1998-11-15
• 3.50 - 1998-11-18
• 3.51 - This Version - 1998-12-28 - includes new version of test suite

Bugs

The list that follows is a list of bugs in the browser, that is, what is described is in error. I have also included a few partially supported features as bugs.

• Last run through entire suite: 3.51
• Last run through existing bugs to see if they still exist: 3.51

0.4

I have to press the "Stop" button to get the page to display. When I do, the page shows up fine.

2.5

Pseudo-elements should not be allowed at the beginning of selectors.

2.6

The extra spacing under first-letter in a large font probably shouldn't appear. -- the default line-spacing for :first-letter should be 1 or slightly less.

4.1.4

• The first test is a mess: the floats are not high enough and should not cause line breaks.
• In the second test, the text should flow around the floats, not through them.
• In the third, fourth, and fifth tests, the floats should be carried to the next line; they should never make their parent expand.
• In the sixth test, the paragraph should be even with the text. (This rule, however, is questionable. See my posts on www-style.)
• In the eighth test, the float inside should not widen the DIV outside.

4.2

• Padding and border of inline elements should not change the line height. (replaced elements excepted)

4.3

auto margins on replaced block level elements make a huge mess. They should not cause the width to change - ever! (They can for non-replaced elements if width is auto.)

4.4

• Padding, border, and margins on inline elements are ignored, except that the margins show up on the right and left.
• The document does not load completely with stylesheets turned on.

4.5

Body margins are displayed as padding.

5.2.2

• font-family: cursive doesn't work very well because the default cursive font is "Times New Roman." Things should come out a little better just using the internal TTF font stuff. Of course, the fonts can be fixed up using a very well hidden part of a dialog box (one doesn't expect the CSS fonts to be underneath all the HTML stuff), but most users won't figure that out.
• The font "serif" should be the same as the default font, at least in the initial configuration. (For me, serif was Georgia, and the default was "Times New Roman.")

5.2.5

• bolder should not be any bolder than bold. It is a relative descriptor, but this misunderstanding may have been due to an early incorrect version of the W3C CSS Test Suite.
• Font weight 500 should probably be rendered as bold, as per the example in the CSS2 spec.

5.2.7, 5.4.8

Backgrounds of inline elements should not cover the line height. The size of the background is determined by the top and bottom padding of the inline element.

5.3.4

The background image tiling runs wider than the paragraph on initial load - it extends to where the paragraph would be without the scrollbars. However, if the scrollbars are removed and brought back, it is OK.

5.4.2

There is extra spacing around the links at the bottom of the page.

5.4.3

Since text-decoration spans children, the image should be underlined. What should have been said was that it should not be overlined.

5.4.4

• The following vertical-align does not work: text-top.
• Middle align should align the middle of the image with the point halfway above the x-height of the parent text.
• text-bottom align is ignoring descenders.
• Percentage aligns appear to be relative to the font-size instead of the line-height.

5.4.5

There is no capital letter after the  , as there should be.

5.4.8

Negative values are not permitted on line-height and should not be converted to positive ones, but, rather, ignored.

5.5.02, etc.

The table width algorithm has problems with CSS margin and padding properties. I also think the TABLEs should, according to CSS, be the whole width of the page, but this is inconsistent with historical behavior.

5.5.02b, 5.5.05b

The right margins on inline elements are being applied on every line.

5.5.04b, 5.5.05b

The negative margin-left causes strange effects at the right edge where there is a line break.

5.5.06, etc.

Negative padding values are not allowed. It causes a number of other problems that I will not mention.

5.5.06b, 5.5.08b

Top and bottom padding on inline elements is not applied. It should at least be applied up to the edge of the text on the next line, but preferably to its full extent.

5.5.10b

When padding is set on all edges of an inline element, the top and bottom padding should not effect the line spacing.

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

• Border on inline elements should not affect the line spacing.
• The line-height should not be treated as padding; if there is no padding set, then the border should touch the text on the top and bottom. However, it should not come closer than that, as it does with double borders in in 5.5.18b and 5.5.20b.

5.5.16, 5.5.16b

Shorthand border-color does not work.

5.5.18, 5.5.19, 5.5.20, 5.5.21, 5.5.22

Table cell borders do not seem to show up, although it may be only the color that doesn't work.

5.5.25c

• The image in the second example should appear after the paragraph. The same type of problem occurs in the sixth example if one makes the window narrow.
• For some reason the page is incorrectly given a horizontal scrollbar and made considerably wider than the viewport, which messes up the floats and certain padding. This is new in 3.51.

5.5.26c

• The floats run all the way across the page. They should carry to the next "line" when they no longer fit within their parent.
• The bottom border of BODY should have space below it when the page is not long enough.

5.6.4, 5.6.6

The list marker images don't have enough padding after them. The idea of the CSS2 marker-offset is what should stay constant.

5.6.5

With a small font, the text inside the table is carried to a second line even though there is room to widen the table. That is, the bullet is not counted in the line-width calculation. (See my comment on 5.5.02, etc.)

5.6.6

There should not be an indent before the marker letter A, because it is simply the first inline box in the line.

7.1

• When an invalid keyword occurs, the entire property declaration should be ignored. This occurs in both the text-decoration and the font properties.
• // is not a valid CSS comment and should result in errors.

Unsupported Features

• Alternate Stylesheets (1.1)
• A: active selector (2.1)
• background-attachment: (5.3.5)
• all values of display: except for block and none, i.e., block and inline (5.6.1)
• white-space: (5.6.2)

Other Bugs I've Heard About (not from CSS Test Suite)

• Opera does not support background-images on TD elements. See a demo by Jukka Korpela. He also shows a workaround. (reported by JK)
• Setting line-height on OL elements causes the numbers/letters not to be baseline-aligned. This is bad behavior, although not strictly inconsistent with the spec, I believe. However, it is inconsistent with the CSS2 marker model, which I think is how lists should be rendered. Sue Sims has a demonstration of this bug. (reported by SS)
• list-style-image marker images are not loaded if the list is within a table. However, if the image is already in the cache, they work fine. (reported on c.i.w.a.s)
• Opera has some problems with the inline box model. However, its performance on my inlinetest is better than any other current browser.
• Opera does not seem to support background color on a tr. I was told this is fixed in 3.51, but I haven't checked. I'm also not 100% sure that background-color should be supported on a tr
• A border on BODY in a short page should have extra margin-bottom.

(Back to CSS Testing Information, David Baron)

LDB, dbaron@dbaron.org