kossae9000 — 2012-05-07T11:48:22-04:00 — #1
For some reason I can't seem to find what is causing the spacing issue on my navigation section in IE8. It's pretty frustrating, as I've tried removing margins and padding of the elements contained in the div. It appears the ul has a top padding or margin, but there is none to be found in the code. The site seems to work just fine in other browsers, even in IE9. Any thoughts? Thanks!
ryanreese — 2012-05-07T14:38:36-04:00 — #2
Another reason you shouldn't use HTML 5 :). It's because you use the <nav> element (with the id="access"). IE8 and down don't support HTML5. If you were to change that <nav> to <div>, it would remove the spacing .
As proof, IE7 is also doing this. IE6, etc.
kossae9000 — 2012-05-07T15:22:54-04:00 — #3
Ahhh, the basic "Toolbox" template I used from Wordpress to design this was using HTML5. Thanks for your help!
ryanreese — 2012-05-07T15:33:12-04:00 — #4
Glad I could be of help :).
webgrid — 2012-05-07T15:48:17-04:00 — #5
Thanks for the info. I have just started to add the nav element for my menus, before reading your post
ryanreese — 2012-05-07T15:51:10-04:00 — #6
This shouldn't just extend to nav elements :). For 90% of HTML elements, there is no real reason to add it in. Perhaps better semantics? Questionable. Stick to HTML4 tags for now :).
webgrid — 2012-05-07T16:07:00-04:00 — #7
I added it for SEO reasons. I had this idea: "Maybe Google can identify my menu more easily if I use the nav tag..."
spritanium — 2012-05-07T17:51:08-04:00 — #8
The usefulness of <nav> is questionable, but HTML5 introduces plenty of new tags and attributes that you can and should be using today.
It's perfectly acceptable to use HTML5, regardless of what some people here might say. Older browsers don't support the new tags, but the web shouldn't be about dumbing down our code to make sure obsolete pieces of software can read it. The web should be about moving forward.
You're right in your assumption that HTML5 elements can help with SEO. It might not make a difference now, but down the road, Google will be taking advantage of the new tags. They might use <nav> to show a list of links in the search result. I can tell you right now they'll be using <time> to organize results based on date. And then the people who insisted on sticking with HTML4/XHTML because "HTML5 is nothing but sloppy code and tags for nothing" will be wishing they'd taken advantage of this stuff earlier on.
The new tags AREN'T for nothing...they have a real purpose, and anyone who doesn't see that purpose can't seriously say that they understand the value of semantics in HTML.
Sure, there's a certain point when a <div> or a <span> or a <p> will do just fine, but things like <header>, <article>, <section>, <aside>, <footer>...they help define the different parts of a page. And don't let anyone tell you that these elements are presentational. They're not. <header>, for example, isn't simply "some **** at the top of my page". It's a space for introductory content. You could technically use CSS to put your header at the bottom of the page, though I'm not sure why you would.
I say use HTML5, use CSS3, and use every excuse to forget about versions of IE that people shouldn't be using anymore in the first place. If even Microsoft wants you to stop supporting IE6 and IE7, it's time to stop supporting them.
Some people say it's the designer's responsibility to make sure anyone can see their design in its full glory...but at the same time, it's the viewer's responsibility to understand how to use a computer properly and upgrade their browser.
Just use an HTML5 shiv, make sure all your content is accessible to everyone (even if it might not look pretty), and you're good. Welcome to the future.
system — 2014-10-07T22:22:24-04:00 — #9
This topic is now closed. New replies are no longer allowed.