Friday, May 13, 2005 (Safari background img bug)
Running into the bug mentioned on this css-discuss archive:
When the container div is set to the exact size of the background image AND the background position is other than 0 0 (px,cm,pt,em) then the background position is ALWAYS repeated, even if position-repeat has been set to no-repeat.
Here’s a related example of the bug (This one happens when the bg img is positioned to anything other than 0 0, and it’s container is smaller than the bg img).
This may be fixed in safari 2? We’re running 1.3 here.
Posted in interweb, macintosh, tech / 11 Comments
11 comments:
Leave a Comment:
Powered by WordPress using the Minimal, Really Theme. Inspired by Things
- Set of iPhone wallpapers / Download (.zip)
joe d #
Maybe adjust your background size/proportion/opacity so that you CAN set the position as 0 0 ?? A link to your page would help.
fred #
i need to brush up on my English more to find out what the hell “Netball” is.
and I too hate the yankees.
joe d #
what the hell is Fred talkin about?
Bill #
He’s referring to the yankee discussion
Sweet Gravatar joe d!
bill #
Setup an example page of the safari bug, in my specific use of it.
A solution would be to keep a container at least 1px wider than a background image contained within. Of course, this can be a pain in the ass.
Can Anyone tell me if this is happening in the latest safari, 2.0?
joe d #
I think you mean safari 1.2 http://www.apple.com/safari/download/
fred #
yeah wrong forum.. just signed up for that gavatar thing.
r00ts #
y r the names and gravatar below the coment, looks weird
joe d #
because weird is ‘in’. duh.
clint #
Safari 1.3 borked my bg rules as I used to use the full shorthand property on each rule as a hook if I ever wanted to add imgs. But once 1.3 came out my bg colors dropped, I found out that using an empty url() would wipe out the bg color, so I had to rewrite all my bg rules on selectors that didnt use a bg img….
Safari 1.3 as far all my modern browser pc/mac testing was the only one who borked this…
Dan Nye #
As far as I can see, Safari 2.0.3 still has this bug… and it’s really annoying.