http://samredman.com/popuppic/popuppic.css != http://samredman.com/popuppic/picpopup.css ;)

¥

Thanks.. ¥åßßå I edited that l now.

What do you think I'm doing wrong here with with putting iit into B2evolution style sheet?

I'm always accused of being obtuse :p

In your html you refer to the latter link ( which is a 404 ), either change the link or rename the file to suit ;)

¥

Ok darn.. I was the one being obtuse. I couldn't see the error even with your example.

Now.. why doesn't in work in B2?

The chances are that with b2e you forgot about <base> ( which points to the current skins folder ;) )

¥

I am going to edit my original post... and maybe show the demo in b2..

ok, I'm probably still being obtuse ( tad hard to tell without a link to the blog page where it fails ;) )

but, in your html you use this :

<link rel="stylesheet" href="popuppic.css" type="text/css"  />

but, b2evo has a <base> tag which makes that link relative to your skins folder ( /skins/custom/popuppic.css is what gets "seen" )

¥

Yes.. thanks so much. It is working now. I actually just needed to get it into some clean css files (rather than some one's I had added to over time).

You can see it here:

http://samredman.com/testdemo/myblog.php

Ok ¥åßßå.. I can reproduce my problem...

It seems that it came from merely my own convoluted css hacking that had produced some conflicts... I am going back to basics and rebuilding some of my css files and I am on the road to having it solved.

Thanks for your help.

Well finally, I figured out the problem... but not the solution:

I found that when I have two css definitions groups in my css file that are probably conflicting because they have similarities that one will override the other.

I have prepared a file with these two groups. If I have them in separately, they both work as designed. If both are in, then only the "button" css group works. Could you take a look at this file and tell me a way I could get both "sets" to work in the same css file?

You can see it here:

http://samredman.com/testdemo/examples/cssexamples.txt

This txt file contains two css groups which can't be in the same css file without conflict. Separately they work well. If both are in only the "button" css will function.

ok, you win the obtuse war :p

it'd help if I *knew* what your problem was, I have no idea what I'm meant to be seeing ;)

btw, this part of your css needs sorting

div.button img { 
border: none; 
width: 120px; 
height: 90px; 
); 
float: left)

¥

Thanks.. yabba (yes, that css needed fixing, or "sorting" as you say ... across the pond).. but that didn't do it. I will fix up a nice demo illustrating the problem (and what examples of the code being used).

In the meantime, I got it to work by changing the class name of that set of div class css from "button" to "zebra" which, of course, makes no sense to me.., but it worked. Later tonight (or tomorrow, I will fix up that demo). I am very anxious to see what you think is making that incompatiblity.

samredman wrote:

I found that when I have two css definitions groups in my css file that are probably conflicting because they have similarities that one will override the other.

The last one in line will we executed or rather: seen. It's just top down to determine the order.
In certain cases this comes in handy because you can override general styling with a style declaration on the page or an inline style.

Good luck