Search results

Marquee really should have been removed a long time ago. Blink still works in FF. Can't imagine why...

Not because I think you should (I don't), but out of simple curiosity, try: <marquee><img src="link/to/image.png" /></marquee> UPDATE: Tried it in Chrome on Codepen.io and it works. Not sure whether I'm happy or sad...

Since it's a child, it'll be 23.88% of the width of the header. Also, if you set the html's width to 1366px, I'm pretty sure the header's % width will be calculated against that, not the viewport, so the site won't resize to fit the window. Unless that's what you were going for...

In the CSS, the width is set using em. It's causing the width of the 2 columns to become more than the width of their parent container. Because em is relative based on font size, this was likely caused by a change in font size. You can change to percentages to keep things under control. Here's a...

http://www.lmgtfy.com/?q=stock+photography http://www.lmgtfy.com/?q=free+clipart

Need iTunes on your website? There's an API for that. Jokes aside, they might have an API, I'm not sure. If not, you can use the HTML5 <audio> element (with an appropriate fallback for IE8 and below) and just add the button for iTunes. I, personally would use the <audio> element with the link...

This is the only place I disagree. However, instead of individual <ul>'s, do one list and style the <li> as the buttons.

No. Keep the comma. In fact, copy the selectors exactly as I rewrote them. You're welcome. The problem here isn't IE. It's actually every other browser lying to you by rendering the code how you want it to look.

I guess I should have been more clear on my joke. The divs inside of divs thing was a joke about code I've seen, not yours. In fact, your HTML is pretty dang clean. There are better ways to do some of it, but all in all it isn't bad. That said, here lies your issue: .search a:link...

IDK. Check your class/ID names and other selectors to make sure you aren't accidentally selecting that nav. I would try giving the buttons at the bottom a new class and select them using only that class. See if it still does it then. Something like: .troubleshoot{ /* yada yada CSS */ } And...

I tried Chrome, IE9 and IE7. Everything looked fine, unless I'm missing something

First of all, page rank is nothing. Period. The only metric you need to know if you're doing well is that 20k visitors per month. Second, if your site is loading slowly and you suspect it's hindering search engines from indexing your site properly, the best way to do this is by hand. Does...

You'll have to use the child selector for the submenu with the :hover state on the main li. Like so: nav li:hover > ul{ display:block; /*whatever else*/ } That causes the child ul to appear when the li is hovered. Should stay after that.

Guess you must have fixed it? Seems fine to me.

It's not "uber", it's "über". :p

IIRC, XSL is like CSS for XML.

There's a paid CMS for non profits called Raiser's Edge. I've heard good things. Never worked with it myself.

I have no way of knowing without looking at everything.

Those aren't languages, they're preprocessors for CSS.

Hopefully this about covers it: