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 Safari.
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.
Permalink
| Safari
| 1 comments
Reported on 28 March 2006
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.
Permalink
| Safari
| 0 comments
Reported on 22 March 2006
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.
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.
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.
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.
Permalink
| Explorer Mac, Safari
| 0 comments
Reported on 20 February 2006
Safari doesn't allow you to set a background image on a textarea.
Test page Workaround is not included
Reported by: Jean-Charles Meyrignac.
Permalink
| Explorer 5-6 Windows, Explorer Mac, Safari
| 2 comments
Reported on 16 February 2006
It is not possible to obtain the correct scrollTop value of a select list in Explorer, regardless of strict/quirks mode. to reproduce, enter the test page, scroll the list a bit, then hit the button. The alert will display 0 value in IE, and correct value in Mozilla based browsers.
Test page Workaround is not included
Reported by: Omry Yadan.
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.
Permalink
| Safari
| 1 comments
Reported on 4 January 2006
A selector that uses both an element's class and id together with a pseudo-element is not recognized by Safari 2.0.2.
Test page Workaround is not included
Reported by: Andrew Vit.
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.
Permalink
| (Orphaned), Safari
| 1 comments
Reported on 6 December 2005
Safari 2.0.2 (416.12) seems to be unable to process the javascript:window.close() function after a form submission. The first time into the test page, the 'close' button works as expected. However after you've used the submit button, it is no longer functional. The click event is firing, but the close request is not being honoured.
Test page Workaround is not included
Reported by: ray berry.
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2, Safari
| 0 comments
Reported on 22 November 2005
Once the background-color is set on an element, subsequent 'background:inherit' rules (even those matching selectors of higher weight) can't cause the element to inherit the color from its parent.
Test page Workaround is not included
Reported by: Pierre Saslawsky.
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2, Safari
| 1 comments
Reported on 21 November 2005
When nesting a form wholy inside a
Test page Workaround is not included
Reported by: Jay Soffian.
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2, Opera, Safari
| 4 comments
Reported on 19 October 2005
The INPUT (type=text/password) field in IE6 (and older probably too) has a top and bottom margin of 1px in both quirks and standard mode. This can cause a not so nice effect.
(ppknote: Opera and Safari have the same problem with the right margin)
Test page Workaround is not included
Reported by: Marcel Lipovsky.
Permalink
| Safari
| 0 comments
Reported on 13 October 2005
When trying to dynamically create radio buttons with createElement() and appendChild() I noticed that the name and type of the radios weren't being appended along with the radio element.
Test page Workaround is not included
Reported by: Calophi.
Permalink
| Safari
| 0 comments
Reported on 11 October 2005
When you have dynamic content on a single page, Safari doesn't always redraw properly to accommodate the new size of the content. Safari will not redraw the scrollbars, and worse, it will completely "freeze" if you have already scrolled down the page and then clicked a link to load new content of a different size. The only way to get the window to redraw is by grabbing the risize handle in the lower right and physically resizing the window.
The workaround consists of using object detection to target Safari, and then "tickling" the window size (i.e., resizing by a pixel and then reverting back to the original window size).
(ppknote: this behaviour seems to occur only in Safari 2.0.1, not in 1.3.1)
Test page Workaround is included
Reported by: Chris.
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2, Safari
| 0 comments
Reported on 20 September 2005
If a page calls window.open(), then submitting a form on that page and returning to it using the "back" button causes the entered form values to be lost.
(ppknote: Safari has a different bug: it doesn't show the form at all when you go back. This has nothing to do with opening a new window.)
Test page Workaround is included
Reported by: Milo van der Leij.
Permalink
| Safari
| 0 comments
Reported on 8 September 2005
Specially crafted :after pseudoelement with <body> may lead Safari 1.2 to crash.
ppknote: Not tested, since I don't have Safari 1.2 available. The bug does not occur in Safari 1.0 or 1.3
Test page Workaround is included
Reported by: Tuomas Starck.
Permalink
| Safari
| 0 comments
Reported on 1 September 2005
When the font size is enlarged in Safari, generated content can cause the text to be pushed outside of its bounding box.
Test page Workaround is not included
Reported by: Aaron Gustafson.
Permalink
| Safari
| 0 comments
Reported on 1 August 2005
Safari will omit the right padding of an element in a floated container if that element has trailing whitespace. Workaround is to ensure any elements with padding have no whitespace before the closing tag.
(ppknote: The test page is a mess in IE Mac, but the bug is not the same)
Test page Workaround is included
Reported by: Alan Harder.
Permalink
| Safari
| 1 comments
Reported on 28 July 2005
If a blur event fires from an input when you close a tab (and not the entire browser), Safari crashes.
Test page Workaround is not included
Reported by: Beau Hartshorne.
Permalink
| Explorer 5-6 Windows, Safari
| 1 comments
Reported on 20 July 2005
In Internet Explorer 6.0 and higher, setting
html, body {position: relative;}
while in strict mode causes the browser to disallow scrolling. I don't know of any real-world applications where this would be a problem, but it's still a bug.
In Safari the entire body disappears if you set position: relative on the HTML first, and then on the BODY. Safari crashes if you check BODY, then HTML, then uncheck BODY.
Workarounds include using quirks mode, or playing it safe and avoiding setting positioning to the html element.
Test page Workaround is included
Reported by: John Hansen.
Permalink
| Safari
| 0 comments
Reported on 24 June 2005
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.
Permalink
| Safari
| 0 comments
Reported on 20 June 2005
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.
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.
Permalink
| Safari
| 0 comments
Reported on 7 June 2005
Wrapping a checkbox form field and descriptive text in a selector that includes a text-indent style definition renders the checkbox unclickable.
This bug is solved in Safari 1.3.
Test page Workaround is not included
Reported by: Amy Neymeyr.
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2, Explorer Mac, Opera, Safari
| 2 comments
Reported on 1 June 2005
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.
Permalink
| Explorer Mac, Safari
| 1 comments
Reported on 9 May 2005
Explorer Mac and Safari also trigger the onload event when you use an internal anchor to jump to. The jump is executed time and again.
(ppknote: This bug is closely related to Setting location.hash to the same value twice causes reload, but it's not quite the same.)
Test page Workaround is not included
Reported by: Benjamin Eric Morin.
Permalink
| Safari
| 2 comments
Reported on 1 April 2005
Safari 1.2 will crash if you try to hide a block level element, such as a div, by setting style.display to 'none', if the element contains the following :after pseudo class:
div:after
{
content: ".";
display: block;
overflow: hidden;
}
Test page Workaround is included
Reported by: sam.
Permalink
| Safari
| 1 comments
Reported on 31 March 2005
The rows collection for tables in Safari is incorrect. It appears that Safari includes <th> elements in the rows collection. Using getElementsByTagName("tr") returns the correct collection.
Test page Workaround is included
Reported by: David Clarke.
Permalink
| Safari
| 2 comments
Reported on 29 March 2005
When loading XML through XMLHttpRequest, the resulting DOM does not allow access to content of elements, which happen to have the same element name in html AND which have an empty content model in html.
Example: the <link>...</link> element from various RSS flavors is not available in Safari, using DOM methods, because an empty <link/> element is defined for html.
Test page Workaround is not included
Reported by: Johannes la Poutr�.
Permalink
| Safari
| 1 comments
Reported on 14 March 2005
When you place a display inline on a fieldset and the form elements within the fieldset are floated, the form elements wont be clickable by Safari.
Using a position relative will fix this.
Test page Workaround is included
Reported by: Paul van Steenoven.
Permalink
| Safari
| 1 comments
Reported on 10 March 2005
​ works only when a text string is present. When the text consists of numbers only it doesn't work.
Test page Workaround is not included
Reported by: Alexander Popov.
Permalink
| Safari
| 5 comments
Reported on 8 March 2005
When swapping images with javascript Safari will stretch the new image to the size of the previous image, unless the previous and new images have different widths AND heights.
Test page Workaround is not included
Reported by: Justin Heideman.
Permalink
| Safari
| 8 comments
Reported on 22 February 2005
Safari doesn't count iframes with display: none at all. They are not represented in the frames array and refreshing the pages in them is impossible, too.
Test page. Workaround is not included.
Reported by ppk.
Permalink
| Explorer Mac, Safari
| 0 comments
Reported on 15 February 2005
Safari and Explorer Mac have trouble with reading JavaScript properties of an entire radio button array.
Test page. Workaround is not included.
Reported by ppk.
Permalink
| Opera, Safari
| 3 comments
Reported on 11 February 2005
The hover selector combined with an adjacent selector (dt:hover + dd { color : red; }) works buggily (Safari) or not at all (Opera), while these browsers support the two of them separately.
Test page. Workaround is not included
Reported by: Randall Hansen.
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.
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2, Opera, Safari
| 1 comments
Reported on 18 January 2005
When navigating between named anchors in IE, the window.location object changes to reflect the change in the URL. This is correct. However, the window.location object should also change when you use the back or forward buttons, or the history.back() and history.forward() methods, to move between these anchors, and in IE 6.0 and IE 6.1, it does not.
Opera has exactly the opposite bug: it never shows the hash.
Test page Workaround is not included
Reported by: Isaac Z. Schlueter.
Permalink
| Opera, Safari
| 4 comments
Reported on 16 December 2004
Anchor (or "#name")links don't work when the target anchor is inside an overflowing element.
Solved in Opera 7.60p3
Test page Workaround is not included
Reported by: Sander Grendelman.
Permalink
| Safari
| 4 comments
Reported on 14 December 2004
When more than one animated GIF features on a page, Safari sometimes does not play the animation.
Test page. Workaround is not included.
Reported by Nic Rodgers.
Permalink
| Explorer 5-6 Windows, Safari
| 2 comments
Reported on 10 December 2004
Setting an inline border style (element.style.border) works in all browsers. Removing it to allow the normal border styles to return, however, is tricky in Explorer Windows and impossible in Safari.
Test page. Workaround is included.
Reported by ppk.
Permalink
| Safari
| 0 comments
Reported on 2 December 2004
When resizing a window vertically through resizeBy, Safari seems to move the entire window instead.
Test page. Workaround is not included.
Reported by ppk.
Permalink
| Explorer 5-6 Windows, Explorer 7 beta 2, Safari
| 6 comments
Reported on 20 November 2004
When you define visibility: hidden on * Explorer Windows and Safari don't show anything ever again.
Test page. Workaround not included.
Reported by Giuseppe Bertone.
Permalink
| Safari
| 2 comments
Reported on 19 November 2004
When you remove the elements of a form, Safari nonetheless keeps references to these removed elements in the document.forms.elements array.
Test page. Workaround is not included.
Reported by Petr Stanicek.
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.