Stupid CSS Bugs
 

Ive had a problem with Firefox placing a blank space underneath images in some of my sites. Some its no problem and Im not bright enough to figure out the difference.

With this site http://www.porncritixxx.com/porncritixxxx-test.html

the second header you can see with FF shows a blank space under each image. In IE it is fine.

My doc type as you can see is declared as..





I'm also having what must be a related problem on this site..

http://www.thaivixen.com/modelsfromthailand.html

The hardlinks on the left are all unintentionally double spaced, even between the same links and line of text. I gave up long ago playing with it but decided to use this design for some new sites and am having the same problem so I'd better address it.


If anybody can show me my errors I'll love you long time :)

Wow, at first blush I don't know what is specifically wrong, and not to sound like an elitist, but you really should start trying to use div's in your css as it would make things much clearer.

My guess however is that it has to do with the way firefox is handling your wrapping of a table within a table. When I extract the table so that it is no longer nested and view it in Firefox with no css stylings inheirited or otherwise it looks just fine.

I take that back, it has to do with your doc type, try


But still, if your styling with css it's in your best interest to get used to divs. :)

On the second one, change:
.left-links { width: 105px; background-color: #7E3517; text-align: left; padding: 1px 1px 1px 2px; }
to:
.left-links { line-height: .9; width: 105px; background-color: #7E3517; text-align: left; padding: 1px 1px 1px 2px; }
Note that all I did was add line-height: .9;

Fucking Preacher beat me to the DOCTYPE change on the first one. Fucker!

Couldn't find the thread I had about CSS so I'll jump on this one. I'm using:

table { background-color:#ffffff; }
td { background-color: #e00000; }

to set some colors on a page but it affects my recip links. What can I do so the recip table links are not affected?

Also, in the following, what is the "th"?

body,td,th {
font-family: Verdana, Arial, Helvetica, sans-serif;
color: #e2e2e2;
}

Is there some way to use "div" to exclude the recip table from the CSS properties?

No, not if the recips are constructed of tables and tds without their own specific class set. Preacher is the expert - I'm just a hack, but since I'm awake and he's busy enjoying the wonderful California sunrise, I'd suggest that you not apply styles generically to tables and tds on your warning page.

th = table header. If you were building a table that was meant to be a chart of some sort, where the first row is comprised of "headings" or "titles" for the information which will follow below it, you'd use th instead of td in your first row.

Well fuck me, I'll never smile again |sad|

Whew! Thanks! I've seen that in a few places and never put it together.

While I have your attention and everyone else is waking up, on this page:

http://www.best-wet-pussy.com/hairy-pussy/

there is a yellow line under the image on the right, in Firefox, but not in IE. How can I get rid of the yellow bar?

I also just noticed the SmutGremlins recip is all fucked up in Firefox...|confused|

Licker, change your Doctype to to resolve both of those issues. (Kill that 'loose' part.)

Well I'll be damned. That fixed it. Who says your useless? I guess I can smile again :D

Now, how can I get the text in my recip table off that nasty blue default color?

For that, I would simply add

a:link, a:active, a:visited, a:hover{
font-size: 14px;
color: #feff01;
font-family: Arial;
text-decoration: underline;
font-weight: bold
}
to your style sheet. That will take care of any link on that page which doesn't have its own specified class.

Where do I send the bill? ;)

|bananna| |bananna| |bananna|
Happy happy joy joy!
|bow|
That worked!

Bill? Hell, I'll take ya in and feed ya!

But damn the pages in that site sure have a lot of code in them. Is that the way I'm gonna have to build sites now? I'ld rather go back to straight html...

Well you can drastically reduce the amount of code in the by saving your CSS info onto it's own page, then referencing it in the with something like this:

So, in your free sites folder, you'd have five pages instead of four.
index.html
main.html
gallery1.html
gallery2.html
lickers.css

That way, you only have to alter the styles once to make site-wide changes. It makes it far simpler when you find yourself adding more and more styles.

So, I put the style sheet in Notepad and save it as lickers.css and upload it as that? And for the mirrors I can use ../(originalsite) to call the style sheet?

The answer is YES. ;) You don't have to call it licker.css. Mine is named cunt.css. Don't believe me? View my source! Anita's Dirty Pillows :D

The other benefit of using an external style sheet is page load times. :)

I absolutely agree with you on divs, but i have a problem where ai always try to kick it old school and thought id be the only guy around to still use tables ;) But as soon as divs become a thing of the past ile be all over them (or i just stop being lazy)

U dub, I owe for that line height bit man. I was using some other line collapse tag that never worked for me, i didn't even know this one existed. I applied the same thing ( line-height: .0; ) to the table containing my header on the porncritixxx page and it worked like a frickin charm.

http://www.porncritixxx.com/asianreviews.html

Thanks to you both for your replies. Next time ile ask here first before pulling whats left of my hair out and putting projects off for months over one little bug :D

Kewl Useful! |cool| Thanks! If you're ever in south Alabama I'll take ya to the Redneck Riviera. (Gulf Shores/Orange Beach area) Maybe hit the Pink Pony Pub and Flora/Bama. |cheers|

Well damn, I knew it wouldn't last. On this page:

http://www.best-wet-pussy.com/hairy-...gallery-1.html

it looks fine in IE but in Firefox there is a short blue line above the word "Here" just under the banner on the right. Wazat?|confused|

Don't fear the code! Make the code fear you!

Anyway, browsers are sensitive about what follows an image - any image.

Change:
to:
The carriage return after the image and before the
is placing space in between the two.

Aw damn. That was too simple. How am I gonna learn all this crap?

Thanks!

Oh, and what's the difference between
and
?

My HTML validator tells me to change my
to
. That's all I know. ;) It also tells me to end my with />, so I do that now too.

If you're using a DOCTYPE that says "XHTML" in it, your validators will tell you that you should close certain html tags. From an explantion on the DigitalPoint forums...

XHTML is html reformulated as xml. XML requires that all tags be closed. Some tags in html are empty, that is they are replaced by whatever they're tagging. For example the is replaced by the actual image,
is replaced by a line-feed, and

---

is replaced by a horizontal line. These tags have no closing tag in html.

XML allows a short-hand for empty elements, the /> mechanism; thus,
. That's good for xhtml, but invalid for html. HTML does allow it, though, if there is a space before the virgule, /. So
fulfills the xml requirement, while being html valid. Using something like

would be invalid, as the closing tag is prohibited, and

is redundant in html and invalid in xhtml.

Also, XHTML is based on XML, so it's much stricter about some other things, like:

- all elements and attribute names must appear in lower case
- all attribute values must be quoted
- non-Empty Elements require a closing tag
- empty elements are terminated using a space and a trailing slash
- no attribute minimization is allowed
- in strict XHTML, all inline elements must be contained in a block element


Personally, I prefer to use HTML 4.01 Strict since the real advantages of XHTML are only available if you serve the pages as ‘application/xhtml+XML’ . If you serve the pages as text/html (which almost everyone does), you may as well be coding in HTML. Documents served as 'text/html' will not be processed as XML, which means that web browsers will not render your pages as XHTML, but rather as HTML and will fall back on error handling and trying to guess how it was meant to be anyway.

Plus, if you do try to serve your pages as ‘application/xhtml+XML’ then Google AdSense and some scripting will not work. For example, document.write, innerHTML (for AJAX), and others.

More on why not to use XHTML here.

I'm sure there are some good reasons why some folks do like to use XHTML and I'll be glad to read about some of those if anyone would like to post about them here.

Well, that explained that |loony| |confused| I'll take your word for it.

Another CSS question: If I use CSS to set a border around an image of say, 2px, do I still need to put border="0" in the line where I set the image width, height, etc? Seems pointless but I saw it done that way on someone's site.

No, css already defines the border so theres no need for the border tag.

You'll find every html tag or property or whatever can be replaced with css and theres much more you can do with css so its worth learning which ones replace which.

For me it was hard to get used to dropping cellspacing and padding and replacing it with css padding and margins. Took a bit to wrap my mind around it. But once I got onto it its been sweet.

And I highly recommend HTML 4.01 Strict over Transitional as with strict your pages will look exactly the same in both FF and IE with one or two minor tweaks declared for the body and or all tables and td's of the page including...

text-align: center;
margin: 0px;
border-collapse: collapse;
vertical-align: top;

and i think...

line-height: 0px;

...but im just learning to play with that one.

Thanks!


Now that sounds nice.

Well, I never thought it would be possible but I'm building sites with external style sheets faster than the old way. Here I sit with a site ready to submit, waiting for the 24 hour clock to tick down so I can get it submitted. This is nice but now I have to find something to occupy my time...|zzzzzzzzz

Get crackin on your next site. :) I've found with the limited css I use it is a plus all the way. I learn a little more as a I go. |headbang|

AAAAARRRRGGGHHHH!! |banghead| |pcsucks| |shocking|

OK, now that I've pulled out ALL my hair and used up my LAST nerve, why would a page look fine in Firefox but have trouble in IE?? I've gone over the CSS line by line and it looks fine. |shocking| I thought Firefox was more critical of errors.

Nevermind...A complete and total reboot fixed things. Go figure...|pcsucks|

Ive found IE to be more critical of errors. But you'll get far less if you go with html strict, but im sounding like a broken record now :)

If I have a background saved as bg.gif, shouldn't this set it as the body background on a page?

body {background-image: url(bg.gif);}

Licker,
That looks like the right syntax. Did you tell it to repeat?
background-repeat: repeat;

http://www.w3schools.com/css/pr_background-repeat.asp

I didn't but just did and still nothing...|huh

Here's the page: http://www.best-wet-pussy.com/lesbian-sweethearts

Ahhhh, wait a minute, lemme delete history, cache, etc. That might be the problem

body
body {background-image: url(bg.gif);
background-repeat: repeat}

Take the first "body" out and put a ; after repeat and see what happens

Well duuuuh, that extra "body" was the culprit. |pokefun| me
(I wish there was a CSS validator)

I thought the ";" was if you were going to add more things to the list of attributes. I put it in and left it out and it didn't affect anything.

Well, that fixed it in Firefox but it's not appearing in IE.

I sent you a copy I made of the page and css that works. Check your mail at aol.

Thanks, I'll take a look

I deleted temporary internet files and deleted history which didn't work. I deleted cookies and that fixed the problem. That and getting rid of the extra "body".

Thanks!

Try this one...
http://jigsaw.w3.org/css-validator/

Also, if you're making changes to an external css file and not seeing the changes in your html page (especially in IE), one thing that often "refreshes" everything is to load your external css file in your browser and then load your html page in the same window. It's harder for IE (and other browsers) to act like they don't know about your changes after you've just rubbed their faces in it.