Nah, they trained IE7 to ignore the prologue, only IE6 goes into quirks from that.
The W3C is 10 years behind themselves.
You never needed the XML prologue. It was a suggestion, mostly for if your XML was UTF-16 or weirder (which you're not sending to a web browser anyway). But XML worked in browsers who parsed XML with or without the prologue. Like a doctype, browsers tend to ignore it. Not sure about other software though.
BTW, you have this tag:
<meta http-equiv="content-type" content="application/xhtml+xml; charset=utf-8" />
Your server is conflicting with this content-type. It's sending an HTTP Header of text/html, which is why your page appears in IE at all. If it really was application/xhtml+xml, IE would instead offer you the possibility to download this "file" with another application (on my work machine it would offer to open with Firefox
The charset you need because your server isn't sending a charset. If it did, though, it would override your meta tag.
And... why state the page is English, when it's Norwegian?
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="no" lang="no">
You later have the content-language meta tag with the correct language but it's unknown if all AT actually read that tag, or if that tag is able to override the lang attribute of the HTML tag.
I do not agree with you in your way of using the h1 tag to style the logo. In my opinion, the heading tags should be used for content, not for presentational elements, as you do when you style the h1 with the logo as background.
Yeah the debate on who gets the h1 seems pretty evenly divided in the web world. Do what feels right here.
When working with design, it's much faster to change the size in the markup then to open the image in Photoshop each time you make a small change. The correct sizes will be applied in the end.
Browsers are worse at resizing images than an image editor. And the larger files you ask us users to download. We managed to make a medium-sized page crawl and scroll choppily in most of our testing browsers on a home-rentals site by having the full-sized images be "thumbnails", though yes these images were pretty big. Shrinking an image slightly is probably not going to crash the space shuttle and cause world chaos and war, but ideally once you know how big you want your images to be, shrink them in your image editor for the love of your users.
In my world it's good practice to use the title attribute when images are links.
It's a terrible practice, but to each his own. Steve Faulkner explains better than any rant of mine. There's also Jakob Nielsen's examples of how titles' tooltips interfere with users being able to read the text of a dropdown, but that's a different kind of menu. This is one of those things WordPress does by default and makes the accessibility nerds go into rage, lawlz.
If that information is important, try a caption. Those work even if the user doesn't use a mouse (though there's a way to display titles with CSS if the user can focus on the element... that's fun to do sometimes).
But still it's a mystery why the menu jumped to the right side only in IE 7. And that was my question.
I wish I had my box with IE7 on it, but looking at the code... you set something to position: fixed but didn't explicitly state where it should go. Most browsers do the right thing and assume left and top, but IE in my experience has needed some extra coordinates, and that might be what's going on here.
Does it fix itself if you add in "left: 0" to #topp? However I might be thinking of IE6 here... that same home-rental site I mentioned earlier had a fixed-position footer (always a bad idea since users can't scroll if their screen's not as wide as the fixed element... but we were stuck with it at the time) and one or some of the IE's really wanted the whole shebang:
left: 0, bottom: 0, right: 0 and explicit width: 100% was all necessary. Again though this might have really been more for IE6's benefit, who doesn't do fixed anyway so I was feeding it position: absolute and often I need explicit left's and right's for those in IE6 as well.
But anyway can't hurt to try it. Being a fixed element, what other elements do or what margins they haven't shouldn't be able to affect it at all. Like position: absolute, fixed elements are entirely out of the flow.