shit, see that's the same thing i was running into before. first link works great and the rest are :screwy:.

 

np.. i write all my code by hand, too. especially with CSS, it's not really possible (yet) for a WYSIWYG editor to handle all of the advanced things. but in all honesty, if you really want to learn more about CSS and web development, you're not going to learn a whole lot and it'll mostly be incorrect if you stick with your ie-is-good-enough mentality. it doesn't hurt to develop web pages that work in as many browsers as possible - you're just maximizing the accessibility potential of your site. if you do choose to do this, you'll realize how much of a bitch it is to develop for IE, NOT the other way around. most CSS and javascript will work fine in firefox/opera/konqueror/safari when you code it one way - this is how it should be. then you put it into IE and everything goes to hell.

firefox is a great browser, but i wouldn't say firefox > *... i will say that * > IE, tho.

 

i really have no problems with IE. i have firefox installed too, along with netscape. IE is just my preferred browser.

hey, run http://www.sicracing.com/index.html through your validator now.

 

I use Mozilla









by firefox

 

Hi, my name is Keith and I use Internet Explorer.

edit: and back to the actual topic.. that's never happened to me

 

you wouldn't run into many problems with IE if you're only developing for IE, because you wouldn't think they're really problems. you'd think it's regular behavior - writing everything wrong for IE, because IE accepts it. well, writing anything wrong still makes it wrong, no matter what program may support it. that's why if you actually learn HTML/XHTML, CSS and javascript the right way first, and then try to use it with IE you'll usually run into a ton of problems.

cool. 2 warnings.. your ampersands aren't escaped. you should also replace <B> tags with <STRONG>, replace <I> with <EM>, <U> with <INS>, and <STRIKE> with <DEL>. the old tags are deprecated, and should eventually be unsupported. there are more deprecated tags than that, but those are the most common ones.

 

:eh: ampersand = "&", and it's not escaped? riiight. i'm using it 1 time, & it's in plain text format. lol

<b>, <i>, <u>, and <strike> are HTML standard and are not going to ever be unsupported.

maybe you should use http://www.htmlhelp.com/tools/validator/ to validate your shit. it can recognize that the only ampersand i have in the entire document, is in plain text.

 

ampersands in HTML plaintext should be escaped as &amp; (there are a couple other versions, too) - the reason is that the ampersand symbol itself is used as an escape character. for example, &gt; is the greater than symbol, &lt; is the less than symbol... there are a lot of special HTML characters, and they all depend on the ampersand. the unescaped ampersand issue is a warning, not an error. meaning that it's not absolutely 100% necessary to escape it in all circumstances. but if you don't do it, it can lead to display problems (yep, it's happened to me before in IE). the only place you shouldn't escape them is inside a preformatted text tag, text area/input tag, URL, or inside a tag attribute. this is a decent list of special HTML characters and their corresponding escape sequences.

edit: you should actually escape ampersands in URL's.

http://www.codehelp.co.uk/html/deprecated.html
which means that no, you can't consider them as part of the HTML standard anymore. while browsers will likely continue to support the old tags, this is in no way guaranteed. people will eventually drop them, so there's just no reason to keep using them. newer tags are more flexible and will be continually developed. CSS support will remain and grow, whereas with deprecated tags, CSS support will either drop entirely or remain where it is now. but if you want your HTML to be obsolete and don't want to take advantage of the new language specifications, suit yourself.

that HTML validator is not very good, and you probably shouldn't use it to validate your shit. i could immediately tell when it didn't say anything about the deprecated tags. there are plenty of free validator programs out there that offer much better results. i'm currently using one that's made as a firefox plugin, and it already beats the crap out of that one.

edit: after going through several other online HTML validators, i think the HTML validator you posted is alright. your site's main page IS valid HTML, but like i said, the ampersands and deprecated tags i mentioned were reported as warnings, not errors, using my validator. it's being more thorough, and telling you about things that others might not.

HTML4 is the last version of HTML that w3c will ever layout. the world is now adopting XHTML, and as it moves farther along, little things like what i've mentioned won't be tolerated anymore. as i've said before, better to learn things the right way first, rather than having to re-learn them later on.