April 19, 2005 at 11 AM
Bugs in Safari 1.3
Fellow web designers might be interested to know that I’ve discovered a bug in the latest version of Safari, which I’ve illustrated here.
Non-web designers will probably want to ignore this entirely and continue surfing at normal velocity.
If you use the CSS attribute opacity to adjust the transparency of an image or a box with a background colour, and that box/image is floated, then changing it to be opaque (opacity: 1) using the :hover pseudo-class causes Safari 1.3 to behave very strangely. This didn’t occur in previous versions. The work-around is to put the item in another container, and either to adjust the container’s opacity while floating the item, or adjust the item while floating the container. (In other words, an item has to have both float and opacity for the bug to occur.)
There is also something funny going on with opacity and non-repeating background images that have been positioned (i.e., are not tiled, and not on the default upper left corner of a box), particularly — or perhaps only — when the box is smaller than the background image.
Previously: On Bread and Loaves Thereof
Subsequently: A Design Blog?
Comments
———
I do not know whether it is bug or not but if you try to click on “2” on the webpage
http://physics.bgu.ac.il/~gedalin/text.html
you get into endless spin of a beachball. There is a simple pdf file behind the link (the same as for “1”). I prepared the page to isolate the problem, which seems to be related to css/rtl/unicde ?
— Michael Gedalin | Apr. 19, 2005 — 1 PM
Luke, you should make sure this registers a trackback with Dave Hyatt’s “Regression Roundup” post:
http://weblogs.mozillazine.org/hyatt/archives/2005_04.html#007981
— Avi Bryant | Apr. 19, 2005 — 2 PM
Already done!
— Luke | Apr. 19, 2005 — 3 PM
I reduced the previous example to the problem of css/first-letter.
— Michael Gedalin | Apr. 19, 2005 — 10 PM