Tyssen

I think to a certain extent you do have to blame the band. They may say they don't support this sort of stuff, but if they were serious about it, they'd have a better agreement with the promoter to guard against this sort of thing happening.

Why do you feel a need to?

What do you mean your editor won't allow PHP? Which editor are you using?

You mean like on this site: http://www.nwfs.com.au/

Of course, no other browser does that.

Same here. Got no idea what you want.

And you've obviously chosen to ignore what I wrote about not using the XML prologue with IE. You need to do some reading about what doctypes are available, how they should be used and in which circumstances and with which mimetype instead of just copying and pasting. For instance, your page will never validate as XHTML1.1 when you're using this: <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />It should be this: <meta http-equiv="content-type" content="application/xhtml+xml; charset=iso-8859-1" />but you can't use that mimetype with IE cos it doesn't understand it.

You need to think about those who with a larger resolution than that though because the width of your layout (and consequently the line-length) is too large. You'd be better having another column in there to make the main column's width smaller.

You've got a valid XHTML 1.1 button on your site yet you've got a HTML 4.0 doctype (it's not valid HTML 4.0 either by the way). And with an HTML doctype you shouldn't have the XML prologue in front of it (you shouldn't have it at all for IE cos it puts it in quirks mode).

I don't know about jail sentences but a lot of countries already have in place anti-discrimination laws (and it doesn't only have to be based on race) which can result in fines (and maybe in extreme cases, jail terms).

You need to put the border on #menu a as well to avoid the jitter when you hover over the links (unless that's the effect you were going for).

I won't bother with a screenshot - it looks nearly identical to FF except maybe 5-10px further in from the side (not worth worrying about).

Don't use absolute positioning for that element. There's no reason to. It should appear where you want it without any positioning at all.

Sorry, you're right. I was looking at the wrong search box.It's the position: absolute that's causing the problem. Remove that, leave the float: right and move the whole <div> to just before your h1. You'll need to do a bit more playing around after that to get it right.

Like WaW says, using an image in the HTML and then using z-index to position text over it would be a dumb way of doing it but if you absolutely had to (although I'd like to hear a good reason why), then you'd also need to use positioning (absolute/relative) to get the two elements to occupy the same space.

I told you yesterday that it's there. Inspiron it's cos you've got Adblock on Opera and Firefox. Scroll down the page in IE and you'll see the search box.

What difference should it make whether they're Indian, Hollywood, Botswanan, Lithuanian or West Papuan? If the copyright is owned by someone, then you can't do it.

What's 'maniental'?

What sort of dog have you got?

Apart from a larger space between the button and the green line in IE it looks the same.

It does show up in IE6 below all the ads.

I've got a site for my freelance web design business and I also run a site for my local community association (hosted with T17). Then there's the sites I've built for other people that I'm the webmaster for but they're not really mine, I'm just the caretaker.

Developing your thinking is an important skill though.

Or not. If you're aware of Frontpage's limitations, why continue to use it?

I'm a graphic/web designer/developer/sub-editor for a book publishing company and do freelance web design in my spare time.