Comments on: MySpace layouts are a pain http://www.bunnyhero.org/2007/03/02/myspace-layouts-are-a-pain/ Notes on Flash and Web development Fri, 21 Nov 2008 23:18:22 +0000 http://wordpress.org/?v=2.6.3 By: onemak http://www.bunnyhero.org/2007/03/02/myspace-layouts-are-a-pain/#comment-666 onemak Sat, 31 Mar 2007 20:50:49 +0000 http://www.bunnyhero.org/2007/03/02/myspace-layouts-are-a-pain/#comment-666 hmm, try the layouts at http://www.rockmyspace.info but i dont know, i m not into myspace too much hmm,
try the layouts at http://www.rockmyspace.info

but i dont know,
i m not into myspace too much

]]> By: Chris Bennett http://www.bunnyhero.org/2007/03/02/myspace-layouts-are-a-pain/#comment-64 Chris Bennett Sat, 03 Mar 2007 01:34:46 +0000 http://www.bunnyhero.org/2007/03/02/myspace-layouts-are-a-pain/#comment-64 One of the best things I've seen is sillyness involving filter:alpha(..), -moz-opacity:.., opacity:.., and/or -khtml-opacity:.. being applied to the _entire_ layout. This causes every Flash object in affected by that style to go completely invisible in Safari, regardless of the actual opacity specified. I've already resorted to inlining border:none on all of our MySpace-bound img's. I'm probably going to force opacity:1 to save Safari, and it sounds like that may be the direction you're going in as well. We used a table approach for a while, and it had a lot less problems than CSS. Having to override stupidity is a pain. The most annoying issue that I didn't predict was the CENTER tag. It pretty much screwed our image overlay positioning via CSS. =[ One of the best things I’ve seen is sillyness involving filter:alpha(..), -moz-opacity:.., opacity:.., and/or -khtml-opacity:.. being applied to the _entire_ layout. This causes every Flash object in affected by that style to go completely invisible in Safari, regardless of the actual opacity specified.

I’ve already resorted to inlining border:none on all of our MySpace-bound img’s. I’m probably going to force opacity:1 to save Safari, and it sounds like that may be the direction you’re going in as well.

We used a table approach for a while, and it had a lot less problems than CSS. Having to override stupidity is a pain. The most annoying issue that I didn’t predict was the CENTER tag. It pretty much screwed our image overlay positioning via CSS. =[

]]>