When creating an object using the inline object syntax, it is possible to use numbers as property names:

var foo = {7:'bar'};

In Internet Explorer for Mac, this will throw a syntax error and cause the entire script to be ignored.

Test page Workaround is included
Reported by: TarquinWJ.

Without an explicit width set, overflow:auto and overflow:scroll do not work in Opera 6.06, 7.23, 7.54 or 8.0. Oddly enough it does work in Opera 7.02, except Opera 7.02 ignores max-width.

Test page Workaround is included
Reported by: Kravvitz.

In Safari 1.2 (and related browsers like OmniWeb and Shiira - but not Konqueror), window.toString() returns an undefined value instead of a string. As a result of this, comparing window to a string, boolean, or number causes Safari to throw an error.

Bug solved in Safari 1.3

Test page Workaround is included
Reported by: TarquinWJ.

Setting multiple interval timers to run simultaneously causes the timers to become completely unreliable in Mozilla/Firefox and iCab.

In most browsers there is a slight variance between the requested timeout and the actual timeout (a few miliseconds per one second timeout). This is normal.

In Mozilla/Firefox, using multiple interval timers causes the intervals to be far too short (a fraction of the requested time), followed by one extremely long interval to make up for the short ones. This pattern then repeats.

Test page Workaround is included
Reported by: TarquinWJ.

When trying to break a list of floats into rows with clear: left on the first cells in the future "rows", the cells after the cleared ones just fill up the remaining space from the previous "rows" as long as the parent's width allows.

Test page Workaround is included
Reported by: Valentin Agachi.

Setting location.hash to the same value twice in succession causes the page to reload.

(ppknote: This bug is closely related to "Using internal link triggers load event", but it's not quite the same.)

Test page Workaround is included
Reported by: TarquinWJ.

When several DHTML layers on top of each other all contain an input field, and one of these layers has overflow: auto the cursor in the other input boxes becomes invisible.

Test page Workaround is not included
Reported by: Murray Hopkins.

When a non-visible overflow, and either left or right padding are used on an element, Mozilla/Firefox over compensates for the required height of the element, and leaves gaps underneath the element's contents.

Test page Workaround is not included
Reported by: TarquinWJ.

The DOM 2 event spec requires that the capture phase event handlers should only be activated on ancestors of the event target, and not the event target itself. Mozilla and Safari break this rule in different ways, and fire it on the event target as well.

Test page Workaround is included
Reported by: TarquinWJ.

When a floated list with overflow: auto; contains a dropdown, the dropdown disappears when changing its value (Mozilla) or never appears at all (Explorer Mac).

Test page Workaround is not included
Reported by: Benjamin.

Setting a border around an iframe creates a padding-right and padding-bottom twice as large as the border.
This bug occurs in MSIE 6 in Strict Mode. It seems the iframe's document width is computed according to the traditional box model, while the iframe itself is computed according to the W3C box model.

Test page Workaround is not included
Reported by: G�rard Talbot..

A background on a TR doesn't work. Instead the TDs inherit the TR's background image.

Test page Workaround is not included
Reported by: Valentin Agachi.