When creating a table dynamically and inserting table rows with table data cells and text nodes and add it to the document tree, it is not displayed at all when you don't include a <tbody> tag. W3C DOM2 methods are used.

(ppknote: Test case does not work in Safari)

Test page Workaround is included
Reported by: Gunnar Vestergaard.

Experimenting with position: relative styles I noticed this inconsistent behavior of IE6. The image on the pages vanishes when a TD is shown/hidden, even though it is not involved in the javascript action.

Test page Workaround is included
Reported by: Chris Seeling.

Opera 8.02 does have a maximum (2048) and minimum (-2048) values for "background-position" property.

If the given value exceeds this numbers, it will be treated as the corresponding extremum. So the declaration:

background-position: 4000px 10px;

will result the same as

background-position: 2048px 10px;

No straight-forward workaround seems to be possible. Consider not using such a large numbers at all.

Limit for IE6 is 100 millions of pixels, literaly.

Test page Workaround is not included
Reported by: Constantine Vesna.

In IE, when a <label> is attached to a <select> element, and the user clicks the label, the <select> is selected, but its selectedIndex becomes 0.

Test page Workaround is not included
Reported by: splintor.

If a page calls window.open(), then submitting a form on that page and returning to it using the "back" button causes the entered form values to be lost.

(ppknote: Safari has a different bug: it doesn't show the form at all when you go back. This has nothing to do with opening a new window.)

Test page Workaround is included
Reported by: Milo van der Leij.

Internet Explorer fails to render backgrounds for elements that have both an ID and a class defined. For instance, #photos.background1 will display the corresponding background in IE6 for Windows, but once that has been defined, #photos.background2, #photos.background3, etc. will not be displayed.

Test page Workaround is included
Reported by: Nathan Smith.

The document.getElementById() function returns an element with a name attribute that is equal to the id specified.

Test page Workaround is not included
Reported by: Chris Bloom.

If you add a class name with a leading space to an element that doesn't yet have a class name, Mozilla ignores the leading space.

x.className += ' over';

This can be a problem if you use a regexp to remove the class name, including the space. The regexp doesn't work in Mozilla.

x.className = x.className.replace(/ over/,'');

Test page. Workaround is not included.
Reported by ppk.

When using a margin on a parent container with a child container inside and in there form elements then the margin of the parent container gets inherited to the form elements, and it can't be removed by a margin 0.

The affected form elements are input types, checkboxes, radiobuttons and textareas

The solution is to put an OVERFLOW: HIDDEN on the child container.

Test page Workaround is included
Reported by: Paul van Steenoven.

In any non-quirks mode doctype, content with position:relative within a block container with overflow: auto, scroll or hidden and a height shorter than its contents, will spill out past the bottom of the container.

Test page Workaround is not included
Reported by: Emmett Pickerel.

On Opera, if a webpage has a CSS with a:visited, a:link that involves changing the size of the element, there is a severe performance penalty when offsetHeight/Width or any type of style reading using getComputedStyle is used in functions.

The style reading functions seem to be executed no less than 150 times slower, and the execution may be up to 350 or more times slower with certain combinations. The interesting point is that, the styles do not need to effect any actual element on the page: #nosuchelement a:visited {...} is enough to cause the slowdown.

Test page Workaround is not included
Reported by: Emrah BASKAYA.

IE 5.5 and 6 set the left origin of the positioning co-ordinates to the edge of the content of the first element of the containing block, and ignore the edge of the relatively positioned containing block.

Strangely ie behaves correctly if the position is set relative to the right edge. It also behaves correctly if the containing block is positioned absolutely.

Test page Workaround is not included
Reported by: Marc Pacheco.

When the font size is enlarged in Safari, generated content can cause the text to be pushed outside of its bounding box.

Test page Workaround is not included
Reported by: Aaron Gustafson.