Bug Reports for iCab

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:

On this page you find the archived bugs for iCab.

Disappearing forms

Permalink | Safari, iCab | 1 comments
Reported on 12 April 2006

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.

:first-line uppercase bug

Permalink | Safari, iCab | 0 comments
Reported on 20 March 2006

In Safari and iCab, text-transform: uppercase does not work when applied to the :first-line pseudo-element.

Test page Workaround is not included
Reported by: Beckley Roberts.

Image Resizing Problems

Permalink | Explorer Mac, Mozilla, iCab | 0 comments
Reported on 17 March 2006

If an image is given various heights, but not a width, browsers enlarge it to fit the ratio of the physical dimensions of the image. But over a certain size, bugs can occur.

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

Incorrect handling of disabled BUTTON elements

Permalink | Safari, iCab | 0 comments
Reported on 23 February 2006

Adding disabled attributes to <BUTTON> elements in Safari does not have the desired effect.

Disabled buttons with text content are not greyed out and still respond visually to clicks (albeit without generating any onclick events).

In <BUTTON> elements with image content, the addition of a disabled atribute has no effect whatsoever.

Test page Workaround is included
Reported by: Philip Ronan.

Multiple interval timers cannot be used

Permalink | Mozilla, iCab | 0 comments
Reported on 23 June 2005

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.