Bug Report - Latest reports
Recently discussed bug reports:
Atom
RSS
This site heavily relies on bug reports created by its readers. Anyone can
report a bug and be published.
Main navigation:
Search reports by browser:
The Bug Report system is entirely dedicated to finding, mending and publishing
CSS and JavaScript browser bugs. Anyone can report bugs,
and I hope that the existence of this system will lead to more and better bug reports.
Below you find the latest bug reports and a few resurrected ones.
In Safari, if you have a form that's inside a div with the clearfix (read about it here) class applied, the form will not show up on the page unless you specifically apply display: block to the containing div.
Test page Workaround is included
Reported by: Amber Rhea.
Let's say that you have an element with an id of id. This element can have either of two different classes, classOne or classTwo. (Either you're swapping the className in script, or it can have different classes on different pages.)
Your CSS might look like this:
#id.classOne { some styles }
#id.classTwo { some different styles }
In MSIE 6, the #id.classTwo style will never be applied - unless it is put in a separate style tag or style sheet.
Test page Workaround is included
Reported by: Isaac Z. Schlueter.
The correct use of the CAPTION element –immediately after the TABLE start tag– causes COL and COLGROUP to become unusable as CSS selectors in the current version of Safari (2.0.3/version 417.9.2).
A workaround is to place the CAPTION after the COL/COLGROUP tags, but this makes the code invalid.
Test page Workaround is included
Reported by: Leif Halvard Silli.
Attempting to get a text input field to expand to fill the browser in a nested table (table-layout: fixed) will cause the input field to overflow its surrounding table cell. Occurs with select boxes as well.
Test page Workaround is not included
Reported by: Matt Wright.
Positioning the legend tag
Permalink
| Explorer 5-6 Windows, Mozilla, Opera, Safari
| 6 comments
Reported on 21 March 2006
Positioning legend tags — what works and what doesn't? To be honest not a lot does.
I've tested — position: absolute, fixed, relative, floats margins and setting widths.
Test page Workaround is not included
Reported by: Marc Pacheco.
Older entries
See the March 2006 archive and beyond.
Below you find a few resurrected bug reports.
IE 7 label bug
Permalink
| Explorer 7 beta 2
| 1 comments
Reported on 6 February 2006
In IE7, if your form is within a table, and your label elements are text-aligned to the right, they do not show properly.
Test page Workaround is included
Reported by: Jeff L.
Radio check moves on reload when form field is removed
Permalink
| Mozilla
| 0 comments
Reported on 2 November 2005
When a form field before a group of radio buttons is removed from the document, and the page is subsequently reloaded, the check mark of the radio buttons moves upward.
Test page. Workaround is not included.
Reported by ppk.
position:relative breaks out of overflow constraints
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2
| 1 comments
Reported on 9 September 2005
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.
position:absolute and overflow:auto causing text box cursor to disappear
Permalink
| Mozilla
| 3 comments
Reported on 17 June 2005
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.
Containing floats inside overflow:auto
Permalink
| Explorer 5-6 Windows, Opera
| 2 comments
Reported on 17 March 2005
When a block set to overflow: auto contains floats Opera and Explorer Windows don't contain the floats correctly.
Test page Workaround is not included
Reported by: Marc Pacheco.
Custom DTDs interpreted incorrectly
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2, Explorer Mac, Mozilla, Safari
| 5 comments
Reported on 2 February 2005
When creating custom DTDs like the one below, all browsers except Opera see the end of the ATTLIST as the end of the DOCTYPE. The result is that they print "]>" on the screen.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
[
<!ATTLIST p behavior CDATA #IMPLIED>
]>
Test page. Workaround is not included
Reported by ppk.