Report a Bug

Return to the Bug Report homepage.

Please report bugs on this site through the normal contact form.

Mystery Bug. How to track down CSS bugs. Required reading if you're new to bug reporting.

On this page you can submit your own browser bug reports. Any bug report MUST include a URL of a test page that you've created specifically for this purpose.

A good test page includes the following:

  1. Code that triggers the bug.
  2. A short description of the bug, which notes all relevant code and browser compatibility patterns.
  3. A fix for the bug, if any.
  4. Contact information so that people viewing your bug report can get in touch with you.

Bug reported. Now what?

Once you've reported your bug it automatically appears as a Draft entry in my Movable Type. Once or twice per week I check the new drafts and the test pages they refer to. If I have questions or comments I'll get back to you, and I may ask you to re-submit your bug report.

Once I have approved your report it's placed in the publication queue. Ideally, I want to release one new bug report every working day. Therefore, even if your bug is approved immediately, it will take a few days before it's actually published, depending on the length of the queue. In general I strive for balance between the browsers in my publication schedule.

I will mail you when your report has been approved and when it appears online.

Report a bug

Fields marked with an asterisk (*) are required.

You

First some personal information. I need your email address to get in touch with you, if necessary. I will not publish it.
Homepage is optional: if you enter a URL your name will link to this URL.

Yes

Title

A good title helps others to quickly find and evaluate your bug report. Please keep it short and to the point. Browser names in the title are not necessary: they appear in the categories.

Test page

A good bug report requires a page that contains a working example of the bug. Please enter the URL of the test page you have created specifically for explaining this bug to other web developers.

Yes

Bug description

The bug description is the main part of the bug report. It should be a summary of the bug. Your bug report page itself should contain a detailed treatment.

Please put all text in <p>'s and all code in <code>. Moderate use of inline HTML elements is allowed.

Affected browsers

Required information: which browsers are affected by the bug?

(Orphaned)
Explorer 5-6 Windows
Explorer 7
Explorer Mac
iCab
IE 8 beta 1
Mozilla
Opera
Safari
other affected browsers:

Preview