croatiankid

It depends on what you use them on. Only IMG and maybe a few other elements have the alt attribute. Most elements (including IMG) have title.

Yeah since IE7 came out I've completely disregarded support for ie5.By the way, if you're being so nitpicky about extra bytes.... can be #id{margin: 0 auto;width:900px;}

not only is it better, it's mandatory because the browser doesn't know 200 of what. the only value you can give w/o a unit is 0.

with utf-8 in html 4.01 strict it validates.

exactly, content (text) and images are copyrighted from the moment you make them.

neither does firefox. but all 3 browsers display a tooltip with title

name is deprecated , id is and should be used instead.

How come it does't work if put before?

IE doesn't like elements with dimensions smaller than the font size, so either setting the font size to 1px (idk if 0 is valid), or line-height, or overflow:hidden should work.

Yeah unfortunately I think IE7 still doesn't support xhtml, and I'm sure ie6 doesn't. It's hard to make good use of technology, which isn't even that new anymore, when the most popular user agent doesn't support it. I mean couldn't they give xhtml support in a service pack at least? Not to mention transparent PNGs, sheesh. However, that does have a solution I read somewhere on msn, I think it uses JS in CSS to get IE to use its PNG transparency thingy (it's not that IE doesn't support transparent PNGs, it's just that it's not enabled by default. Why? I don't think MS' developers know {no offense intended if there are any here}).

it might be because one of them gives LIs padding, the other gives them margin (not sure which gives which). Here's a tip for you that will make CSS so much easier in the future: when you just start making your CSS, the first line you shouuld put in is *{padding:0;margin:0;} That gets rid of any browser-default paddings and margins, and if you give an element padding-top:5px;, it will have 5 px of padding in every browser.

That would be semantically incorrect. Try setting the link via CSS to display:block;

well actually since your sending it as text/html, it isn't really valid xhtml, because it's not being sent as xhtml at all. browsers are recieving it as html. however, if you were to change it to an xhtml or xml MIME type, it would most likely break in ie6, which you definitely don't want lol

i don't know if you have spaces up and down, or left and right, but try this anyway:first try adding to your CSS #tabela img{display:block;} if that doesn't work, then try #tabela li {display:block;} , if that doesn't work, then you will have to delete all spaces in your html code between UL and /UL, making <ul id="nav"><li><span>Sekcja</span><ul id="tabela"> <li><a href="1"><img src="sklad2_17.jpg" height="13" /></a></li><li><a href="2"><img src="sklad2_18.jpg" height="16"/></a></li><li><a href="3"><img src="sklad2_19.jpg" height="15" /></a></li><li><a href="4"><img src="sklad2_20.jpg" height="17" /></a></li></ul></li></ul>

it's not a problem with firefox. you should take a look at this.

block level elements are supposed to be centered with margin:0 auto ,inline with text-align:center;

absolute or relative positioning, and z-index.

I only use XHTML in applications (in combination with XML and/or MathML...), and in CMS. Also I always use a full strict doctype to avoid quirks. Indeed people say that XHTML is the future, and perhaps it is. But if you don't use it as it was intended to (in combination with XML technology), there's no benefit.

Why are you even using Xhtml 1.1 when your serving it as text/html?

that's because you're using a strict doctype.

what doctype are you using?

actually HTML 4.01 DTDs (http://www.w3.org/TR/html4/loose.dtd, http://www.w3.org/TR/html4/strict.dtd etc) say you must have correctly nested tags, so this is not an advantage.The only real advantage is that you can use it with XML, which people rarely do...Take for example http://www.croatiankid.com/, my site. There is absolutely no reason to convert it to XHTML. In fact, if I were to make it XHTML, the total file size would actually increase.An example of the advantages is you can use MathML with it.Oh yeah, one more thing: Internet Explorer 6, the most popular browser in the world, doesn't support XHTML by default (1.0 strict should have a "application/xhtml+xml" MIME type, 1.1 must).Also, you should read this: sending xhtml as html considered harfmful

I always start with that when making a new cascading stylesheet. It's easier to make the page render the same in all browsers, and it saves a lot of filesize doing this than writing {padding:0;margin:0} for every selector and element/id.

Impossible.

okay first we need to validate your code. http://validator.w3.org/check?uri=http%3A%...FTMT%2Fnews.htm is the URL. For starters, you're using an HTML DOCTYPE, but have XHTML elements, like XMLNS and XML:LANG; get rid of them. change get rid of the backslash in <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> in HTML METAs and LINKs don't need to be closed. Then get rid of </link> . You cannot use a specific ID more than once in the same document. The whole point of IDs is they're unique for one element on the page. change them to CLASSes and update your CSS accordingly (change the relevant #s to .s).error 26: you have messed up comments, looking like <!---comment--->[code]. Comments are supposed to follow this scheme: [code]<!--comment--> . notice there are only two dashes on each side, not three.