Bug Reports for Mozilla

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 Mozilla.

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.

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.

Shrinking of children of floated/absolute elements

Permalink | Mozilla | 0 comments
Reported on 13 March 2006

A floated or absolutely positioned element does not have a width and is stretched up by an image. When the image is swapped for a far smaller image, the parent element's width should diminish. Mozilla, though, doesn't diminish the width of the other elements in the floated element, and therefore the parent element retains its original width.

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

:first-letter bug in Mozilla Firefox

Permalink | Mozilla | 2 comments
Reported on 21 February 2006

In Mozilla Firefox 1.5 when you scroll the form so that it is off-screen at the top then scroll back on-screen the underscores on the first letter of each line sometimes do not re-appear again. When scrolling to the end of the form and backup again, and when the browser window is resized to a smal size it seems even more persistent. This bug is triggered by styling label:first-letter {text-decoration: underline}.

(ppknote: This bug is quite flighty, I myself saw it only the third time I tried the test page.)

Test page Workaround is not included
Reported by: Johan Van Den Rym.

z-index/scrollbar flickering

Permalink | Mozilla, Safari | 1 comments
Reported on 13 February 2006

Moving a div with visible scrollbars under any content causes flickering. Easy workaround: apply overflow: hidden; to moving div

Firefox specific bug

ppknote: Safari is also a bit hesitant, though the bug is different from Mozilla's.

Test page Workaround is included
Reported by: Pawel Matyjasek.

clear:both margin bug?

Permalink | Mozilla, Safari | 5 comments
Reported on 3 January 2006

While comparing IE and Firefox 1.5 I found a different behaviour of FF 1.5 to FF 1.0.7.

Using Floats and an end div with clear both with a margin will show different behavior on different browsers. Especially using clear and minus margin in Firefox will not work, FF ignores minus margin in combination with clears.

Test page Workaround is included
Reported by: Thomas Vavra.

mouseover on anchor and return value

Permalink | Explorer 5-6 Windows, Explorer 7 beta 2, Explorer Mac, Mozilla | 0 comments
Reported on 14 December 2005

An event handler for onmouseover an anchor should not show the URL in the status bar when you return false, and it should when you return true, but actually it does exactly the opposite.

Test page Workaround is not included
Reported by: Lal.

Fieldsets count as form fields

Permalink | Explorer 5-6 Windows, Explorer 7 beta 2, Explorer Mac, Mozilla, Opera | 1 comments
Reported on 25 November 2005

Explorer Windows and Mac, Mozilla and Opera see <fieldset>s as form fields, even though the spec doesn't mention them in the list of control types.

Mozilla and Opera allow change events on <fieldset>s, even though they don't make sense.

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

extraneous and erronous Mozilla mouseover and mouseout

Permalink | Mozilla | 2 comments
Reported on 24 November 2005

Mozilla sends extraneous events with improper and invalid event.relatedTarget values instead of generating simple pairs of mouseover/mouseout events.

Test page Workaround is included
Reported by: Garret Wilson.

Long option cut off if form placed in short div

Permalink | Explorer 5-6 Windows, Explorer 7 beta 2, Mozilla | 0 comments
Reported on 23 November 2005

When a drop-down menu has a long option, and the form is placed inside a div of a shorter width, the option is cut off when the user scrolls far enough to the right.

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

Options drop-down menu bug

Permalink | Mozilla | 0 comments
Reported on 7 November 2005

If options in a form are given a large enough height and there are too many options to fit the screen, Firefox will display the menu upwards, leading to it being cut off.

(ppknote: Mozilla is the only browser that honours a height on options. Nonetheless this is certainly a bug.)

Test page Workaround is included
Reported by: Chris Hester.

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.

Leading spaces in class names not added

Permalink | Mozilla | 4 comments
Reported on 13 September 2005

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.

overflow: auto elements and mouseout on layers

Permalink | Mozilla | 2 comments
Reported on 30 August 2005

A scrollable element (overflow: auto) triggers a mouseout event on an overlaying layer, even when the mouse doesn't move outside the layer.

Test page Workaround is not included
Reported by: Stefan Jaeger.

offsetTop and borders

Permalink | Explorer 5-6 Windows, Mozilla | 3 comments
Reported on 29 August 2005

Firefox and IE don't take the border width into account when calculating the offsetTop and offsetLeft JavaScript properties of an element.

ppknote 4/feb/06: JavaScript error in test page. Useless in IE.

Test page Workaround is included
Reported by: Chad Plummer.

Wrong offsetWidth on absolute elements

Permalink | Mozilla, Opera | 4 comments
Reported on 3 August 2005

When an element is positioned outside its parent element, Mozilla gives 0 as offsetWidth, Opera -1.
Mozilla also gives incorrect values, when some part of element is on the border of element. It gives back the size of "visible" area in parent element. So when half is in and half out, it gives half of the real width.

Test page Workaround is not included
Reported by: Mojmir Nebel.

display:-moz-inline-box + text-align = bug

Permalink | Mozilla | 0 comments
Reported on 1 July 2005

Text inside a display:-moz-inline-block element cannot be aligned. Not only that, it doesn't do word wrapping.

Test page Workaround is not included
Reported by: Jordi Pujalte.

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.

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.

Padding and overflow causes gaps

Permalink | Mozilla | 3 comments
Reported on 15 June 2005

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.

Handler for event target is executed during the capture phase

Permalink | Mozilla, Safari | 0 comments
Reported on 13 June 2005

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.

Disappearing dropdown in lists

Permalink | Explorer Mac, Mozilla | 1 comments
Reported on 6 June 2005

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.

Padding difference with windows and linux

Permalink | Mozilla | 6 comments
Reported on 25 May 2005

Using firefox in Windows and Linux (same version) i get a problem where i cannot specify a shadow underneath text to be consistent, because the margin/padding differences are throwing me out - i have set paddings and margins of all elements to 0 - except the one i wish to change... it's highly annoying!

Test page Workaround is not included
Reported by: Tim.

(ppk disclaimer: I don't have a Linux test box, so I couldn't check this bug report)

Window.opener.closed behavior differs among browsers

Permalink | Explorer 5-6 Windows, Mozilla, Opera | 0 comments
Reported on 18 May 2005

window.opener.closed works in IE 6 but not in Mozilla or Opera due to a known bug. Also, in IE 5 window.opener.closed DOES NOT work correctly due to another known bug. I also have a longer writeup in my blog.

Test page Workaround is included
Reported by: Yakov Shafranovich.

li {overflow: auto} generates unnecessary horizontal scroll bar

Permalink | Mozilla | 1 comments
Reported on 25 April 2005

When an li element is set to overflow: auto Firefox creates a horizontal scroll bar in most cases. Short entries not containing block level tags don't suffer from this problem.

The workaround is to wrap the content of a list item in a div and set the overflow on the div instead.

(ppkwarning 03/06: the test page now seems to contain a malicious iframe.)

Test page Workaround is included
Reported by: Marc Pacheco.

Disappearing select box text within block labels

Permalink | Mozilla, Opera | 1 comments
Reported on 15 March 2005

When using an attribute selector like label[accesskey] in conjunction with the display: block: on a label element, a child select box will go blank and/or act strange in mozilla/firefox.

In Opera the last two "act funny" boxes also act funny.

Test page Workaround is included
Reported by: Brian Latimer.

Capitalizing "text-transform: capitalize"

Permalink | Mozilla, Opera | 2 comments
Reported on 11 March 2005

If the string "text-transform: capitalize" is text-transformed to capitalize, should the "t" of "-transform" be capitalized, too?

Opera and Mozilla say No, but they're in the minority. Therefore this is officially a bug in Opera and Mozilla.

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

Hovering over node when it's above an overflow:auto node

Permalink | (Orphaned), Mozilla | 1 comments
Reported on 23 February 2005

Hovering over a node doesn't count as a hover over its parent when it is positioned above an element with overflow:auto. The practical use for this technique lies in CSS menus on sites that make use of the pre element.

Test page Workaround is not included
Reported by: Damien Bezborodow.

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.

Box model of TDs

Permalink | Explorer 5-6 Windows, Explorer 7 beta 2, Explorer Mac, Mozilla, Opera | 0 comments
Reported on 14 January 2005

The box model of a td turns out to be unchangeable in Explorer (Win and Mac), Mozilla and Opera. Explorer Mac forces it into the traditional model, while the other browsers force it into the W3C box model.

Therefore you can't switch the box model of a td, something that is possible for any other element.

Explorer Windows, though, switches the TDs to the correct box model when you use table-layout: fixed. Unfortunately this does not work in the other browsers.

Test page. Workaround is included only for Explorer Windows.
Reported by ppk.

Float following header is buggy

Permalink | Mozilla | 6 comments
Reported on 24 December 2004

When a floating box appears directly after a header in Mozilla, the very first line of text after the float doesn't obey the float but is rendered right through the floating box.
The first floating box on a page is never affected by this bug, though.

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

Text node maximum size

Permalink | Explorer Mac, Mozilla, Opera | 2 comments
Reported on 17 December 2004

Mozilla and Opera split up one huge text node into several smaller text nodes. Explorer Mac acts weirdly.

Maximum text node sizes:

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

Tables and relative position

Permalink | Explorer Mac, Mozilla | 0 comments
Reported on 9 December 2004

Mozilla doesn't honour a position: relative on a table, which can therefore never serve as a container for absolutely positioned elements. This is a deliberate choice, and not a bug, oddly.

Test page. Workaround is not included.

On the other hand, Explorer Mac behaves as if every table has a position: relative. It always positions absolute layers in the table relative to the table, even if they should be positioned relative to the browser window.

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

Dynamic first-line/letter bug

Permalink | Mozilla | 1 comments
Reported on 1 December 2004

When seting class names dynamically through JavaScript, Mozilla doesn't apply the first-letter and first-line styles.

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

document.write xml prolog

Permalink | Mozilla | 5 comments
Reported on 18 November 2004

If both a strict XHTML doctype tag and an XML prolog are written into a popup using separate document.write commands, Mozilla/Firefox/Gecko based browsers will revert to quirks mode, instead of standards compliant mode.

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

font-weight: 600 and font-weight: bold

Permalink | Explorer 5-6 Windows, Mozilla, Opera | 1 comments
Reported on 17 November 2004

font-weight: 600 and font-weight: bold are not equivalent. The browsers stretch up their fonts when you use 600. For a really correct bold font you must use bold or 700.

Mozilla exhibits a similar bug only on Mac: any text with font-weight: 600 appears as normal, non-bold text.

Test page. Workaround is included.
Reported by ppk.

Buttons and font size

Permalink | Explorer 5-6 Windows, Explorer 7 beta 2, Explorer Mac, Mozilla | 3 comments
Reported on 7 November 2004

When you change the font size of button elements, odd things start to happen in IE Win & Mac, and Mozilla. Of course, each browser has its own take on 'odd things'. The Mozilla problem is solvable.

Test page. Workaround is included.
Reported by ppk.

innerHTML in XHTML pages

Permalink | Mozilla, Safari | 9 comments
Reported on 2 November 2004

Handling of innerHTML in XHTML pages (with MIME type application/xhtml+xml) is weird. Getting works, setting doesn't.

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

Box model of form button

Permalink | Explorer 5-6 Windows, Explorer 7 beta 2, Mozilla | 3 comments
Reported on 30 October 2004

Any button uses the traditional box model instead of W3C's, regardless of rendering mode.

Test page. Workaround is included.
Reported by ppk.

document.onclick firing twice

Permalink | Mozilla | 0 comments
Reported on 28 October 2004

When you define a document.onclick before the page has loaded completely and you use the Netscape 4-required captureEvents method, Mozilla fires the event handler twice on every click. This is apparently a very old bug.

Test page. Workaround is not included.
Reported by Matthieu Haller.