<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Design - SEO - Technology ReviewsPosts tagged XHTML</title>
	<atom:link href="http://www.bliznet.com/tag/xhtml/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bliznet.com</link>
	<description>Internet marketing and web design experience.</description>
	<lastBuildDate>Sat, 07 Jan 2012 21:44:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Valid Flash Embed and Preloaders Episode V: Internet Explorer Strikes Back</title>
		<link>http://www.bliznet.com/valid-flash-embed-and-preloaders-revisited/</link>
		<comments>http://www.bliznet.com/valid-flash-embed-and-preloaders-revisited/#comments</comments>
		<pubDate>Tue, 02 Nov 2010 17:45:10 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Embed]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[Internet Explorer]]></category>
		<category><![CDATA[Javascript]]></category>
		<category><![CDATA[preload]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=796</guid>
		<description><![CDATA[If you saw my previous post on valid Flash embed while maintaining preload functionality and used it, be warned: when the user does not have Flash, a lovely &#60;![endif]--&#62; will appear in IE where the Flash movie would normally be. The only way around it I&#8217;ve found is to actually duplicate everything from the opening [...]]]></description>
			<content:encoded><![CDATA[<p>If you saw my previous post on <a href="/valid-flash-embed-and-preloaders/">valid Flash embed while maintaining preload functionality</a> and used it, be warned: when the user does not have Flash, a lovely <code>&lt;![endif]--&gt;</code> will appear in IE where the Flash movie would normally be. The only way around it I&#8217;ve found is to actually duplicate <em>everything</em> from the opening <code>object</code> tag to the closing one so there is one each for IE and Firefox. For example:</p>
<pre>&lt;!--[if !IE]&gt;--&gt;
&lt;object data="movie.swf" type="application/x-shockwave-flash" width="725" height="235"&gt;
	&lt;param name="movie" value="movie.swf" /&gt;
&lt;/object&gt;
&lt;!--&lt;![endif]--&gt;
&lt;!--[if IE]&gt;
&lt;object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="725" height="235"&gt;
	&lt;param name="movie" value="movie.swf" /&gt;
&lt;/object&gt;
&lt;![endif]--&gt;</pre>
<p>Definitely a pain, but I&#8217;ve found no other way around it.</p>
<p>Also in my search for a solution, I discovered that our old pal Internet Explorer does not let you append anything but <code>param</code> elements to <code>object</code> elements in Javascript. That was pretty frustrating. Don&#8217;t try that. It doesn&#8217;t work.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/valid-flash-embed-and-preloaders-revisited/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Pesky iframe and XHTML Strict</title>
		<link>http://www.bliznet.com/the-pesky-iframe-and-xhtml-strict/</link>
		<comments>http://www.bliznet.com/the-pesky-iframe-and-xhtml-strict/#comments</comments>
		<pubDate>Sat, 30 Oct 2010 19:30:44 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Conditional Comments]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Iframe]]></category>
		<category><![CDATA[Internet Explorer]]></category>
		<category><![CDATA[Object]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=736</guid>
		<description><![CDATA[Update: Example code updated. It used the shortened form of iframe before, as in &#60;iframe /&#62;. That doesn&#8217;t sit well with IE. It now uses &#60;iframe&#62;&#60;/iframe&#62; which works. The same goes for object. It similarly does not play well with Firefox 4 (perhaps even lower versions) in shortened form. If you&#8217;ve done much web work [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Update: Example code updated. It used the shortened form of <code>iframe</code> before, as in <code>&lt;iframe /&gt;</code>. That doesn&#8217;t sit well with IE. It now uses <code>&lt;iframe&gt;&lt;/iframe&gt;</code> which works. The same goes for <code>object</code>. It similarly does not play well with Firefox 4 (perhaps even lower versions) in shortened form.</strong></p>
<p>If you&#8217;ve done much web work before, you&#8217;ve probably, at some time or another, had to use an <code>iframe</code>. It&#8217;s not pretty, but sometimes it&#8217;s the only choice, such as embedding a widget from another site or displaying things such as real estate listings. One of my biggest problems with it is that it doesn&#8217;t exist in the spec for XHTML Strict! It exists in Transitional, but I don&#8217;t like to use it. That may be good enough for some developers, but certainly not for me. How about you?</p>
<p>In Internet Explorer 8 (and possibly IE7, but I have not tested it) and Firefox, you can use the <code>object</code> element to embed a web page just like an <code>iframe</code>; however, IE gives it a thick, lovely border that seems impossible to remove. Here&#8217;s the trick: employing IE&#8217;s conditional comments, use an <code>iframe</code> for IE and an <code>object</code> for everything else. Here&#8217;s an example:</p>
<pre><code>&lt;!--[if !IE]&gt;&lt;!--&gt;&lt;object data="http://www.bliznet.com/" type="text/html" width="320" height="240"&gt;&lt;/object&gt;
	&lt;!--&lt;![endif]--&gt;
&lt;!--[if IE]&gt;&lt;iframe frameborder="0" src="http://www.bliznet.com/" width="320" height="240"&gt;&lt;/iframe&gt;
	&lt;![endif]--&gt;</code></pre>
<p>Valid XHTML Strict! Make sure to keep your settings the same across both elements to keep it consistent.</p>
<p>Happy coding!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/the-pesky-iframe-and-xhtml-strict/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Valid Flash Embed and Preloaders in Internet Explorer</title>
		<link>http://www.bliznet.com/valid-flash-embed-and-preloaders/</link>
		<comments>http://www.bliznet.com/valid-flash-embed-and-preloaders/#comments</comments>
		<pubDate>Fri, 18 Jun 2010 18:56:32 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Conditional Comments]]></category>
		<category><![CDATA[Embed]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[Internet Explorer]]></category>
		<category><![CDATA[Preloader]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=731</guid>
		<description><![CDATA[Hello once again, web friends. Today I bring tidings of Flash preloaders and validity. You may have noticed that with the embed code from my YouTube article that Flash movie preloaders don&#8217;t work in Internet Explorer, and the movie has to load entirely before it even displays at all. This is because Internet Explorer requires [...]]]></description>
			<content:encoded><![CDATA[<p>Hello once again, web friends. Today I bring tidings of Flash preloaders and validity.</p>
<p>You may have noticed that with the embed code from my <a href="/valid-flash-embed/">YouTube article</a> that Flash movie preloaders don&#8217;t work in Internet Explorer, and the movie has to load entirely before it even displays at all. This is because Internet Explorer requires a different attribute and the removal of another in the <code>object</code> tag to let preloaders work properly. However, with different attributes, the Flash movie will not display at all in Firefox, so we must use Internet Explorer&#8217;s <a href="http://msdn.microsoft.com/en-us/library/ms537512(VS.85).aspx">conditional comments</a> to utilize two different opening <code>object</code> tags. Behold:</p>
<pre><code>&lt;!--[if !IE]&gt;--&gt;&lt;object data="yourmovie.swf" type="application/x-shockwave-flash"
	width="320" height="240"&gt;&lt;!--&lt;![endif]--&gt;
&lt;!--[if IE]&gt;&lt;object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
	width="320" height="240"&gt;&lt;![endif]--&gt;
	&lt;param name="movie" value="yourmovie.swf" /&gt;
	&lt;param name="quality" value="high" /&gt;
&lt;/object&gt;</code></pre>
<p>The first line is the original that works in both IE and Firefox but doesn&#8217;t allow preloaders in IE. The second is the IE-only method that works with preloaders. Note the lack of a <code>data</code> attribute and the addition of a <code>classid</code> attribute.</p>
<p>Well, there you have it. Venture forth and embed Flash validly with preload animations!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/valid-flash-embed-and-preloaders/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Semantic Markup &#8211; Why Should You Use It?</title>
		<link>http://www.bliznet.com/semantic-markup/</link>
		<comments>http://www.bliznet.com/semantic-markup/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 16:00:42 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Data Extraction]]></category>
		<category><![CDATA[Semantic Markup]]></category>
		<category><![CDATA[Semantics]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=529</guid>
		<description><![CDATA[Why should you use semantic markup when designing your website pages?]]></description>
			<content:encoded><![CDATA[<p>Your markup should have meaning. Markup your content appropriately (e.g. put your address and phone number in the <code>address</code> element) and it becomes much more readable to search engines and other software used for data extraction. Using only <code>div</code> and <code>span</code> elements leaves much to be desired, semantically speaking. These elements are certainly indispensable, however, there are some cases where there are more meaningful elements to use. For example:</p>
<ul>
<li>Use <code>h1</code> as your page title; use <code>h2</code> and on appropriately as sub-headings on the page. This provides an outline of your document.</li>
<li>Use lists (<code>dl</code>, <code>ol</code>, <code>ul</code>) instead of manually placing numbers or bullets.</li>
<li>Use <code>address</code> for any contact information on your page, including physical address, email address, phone numbers, and whatever else you would consider to be contact info.</li>
<li>Use <code>table</code> on data best represented in rows and columns. Use <code>thead</code> and <code>th</code> to markup the column headings and <code>tbody</code> for the data itself.</li>
</ul>
<p>Check the <a href="http://www.w3.org/TR/html401/struct/text.html">HTML spec</a> for additional meaningful elements and get to work! <img src='http://www.bliznet.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>You can use the W3&#8242;s handy <a href="http://www.w3.org/2003/12/semantic-extractor.html">Semantic Data Extractor</a> tool to test your new semantic web site to give you an idea of how it would be seen by software.</p>
<p>That does it for now. See you next time! Until then, read <a href="http://www.bliznet.com/seo-and-validation/">SEO and Validation</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/semantic-markup/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Valid Flash Embed &#8211; Make That YouTube Embed Valid!</title>
		<link>http://www.bliznet.com/valid-flash-embed/</link>
		<comments>http://www.bliznet.com/valid-flash-embed/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 03:11:58 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Embed Code]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Markup]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Validation]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=524</guid>
		<description><![CDATA[Find out how to make that YouTube embed valid.]]></description>
			<content:encoded><![CDATA[<p>Hola! It&#8217;s been a while. I&#8217;ve got another gripe, and this time it&#8217;s with Flash embed code!</p>
<p>Most of the embed code I see for Flash movies is invalid, usually containing the non-existent <code>embed</code> element or some-such. Even the code provided by YouTube for embedding videos contains <code>embed</code>. This can easily be thrown out and will—probably most of the time—instantly make your code valid.</p>
<p>Here&#8217;s an example (in XHTML) of a valid Flash embed that works in at least IE6+, Firefox, and Safari:</p>
<p><code>&lt;object data="flash.swf" type="application/x-shockwave-flash" width="320" height="240"&gt;<br />
&lt;param name="movie" value="flash.swf" /&gt;<br />
&lt;/object&gt;</code></p>
<p>That&#8217;s all there is to it. Adjust the parameters and add additional <code>param</code> elements as necessary. If your Flash movie requires variables, just add an extra <code>param</code> as follows:</p>
<p><code>&lt;param name="flashvars" value="arg1=foo&amp;amp;arg2=bar" /&gt;</code></p>
<p>If you place additional elements inside the <code>object</code> element, it will act as a fallback, displaying if the Flash plugin isn&#8217;t installed. For example:</p>
<p><code>&lt;object data="flash.swf" type="application/x-shockwave-flash" width="320" height="240"&gt;<br />
&lt;param name="movie" value="flash.swf" /&gt;<br />
&lt;img src="fallback.jpg" alt="Flash Didn't Load!" /&gt;<br />
&lt;/object&gt;</code></p>
<p>That&#8217;s all for now. Happy coding!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/valid-flash-embed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CSS Float Trick</title>
		<link>http://www.bliznet.com/css-float-trick/</link>
		<comments>http://www.bliznet.com/css-float-trick/#comments</comments>
		<pubDate>Thu, 10 Sep 2009 19:14:17 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Trick]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=260</guid>
		<description><![CDATA[How to make a list of items appear side by side without and empty div.]]></description>
			<content:encoded><![CDATA[<p>Do you ever have a list of items (such as a <code>ul</code>) in which each item is floating to make them appear side-by-side (an example is the list of sites at <a href="http://www.blizzarddigital.org/">BlizzardDigital.org</a>)? Tired of using a <a href="http://www.bliznet.com/semantic-markup/">non-semantic</a>, empty div after the <code>ul</code> to clear the items? A useful trick is to add <code>float: left;</code> to the <code>ul</code> itself. This fits the <code>ul</code>&#8216;s box around its inner items. Without <code>float</code> specified, the <code>ul</code>&#8216;s box does not wrap around its items at all, making everything on the page after it scoot up behind all the list items. Very annoying. The normal fix for this would be to make the following element clear, but this isn&#8217;t always desirable. Your options are probably to have an empty div after it specifically to clear it (yuck) or make the probably unrelated following element clear it (yuck also). Just float the containing element (in my example, a <code>ul</code>) and set its width to 100%. The width makes sure no one squeezes in on the sides and therefore no clearing is necessary.</p>
<p><em>Clear</em> as mud, right? <img src='http://www.bliznet.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/css-float-trick/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SEO and Validation</title>
		<link>http://www.bliznet.com/seo-and-validation/</link>
		<comments>http://www.bliznet.com/seo-and-validation/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 18:01:52 +0000</pubDate>
		<dc:creator>David Blizzard</dc:creator>
				<category><![CDATA[SEO]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Validation]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=218</guid>
		<description><![CDATA[There is a reason to write valid html xhtml and css even for SEO.]]></description>
			<content:encoded><![CDATA[<p>I was reading <a href="http://www.seowizz.net/2009/08/the-truth-about-validation.html">The Truth About Validation</a> and I felt the need to respond. First off, Tim makes some valid points but only if the article is renamed &#8220;The Truth About Validation and SEO&#8221;. I agree, if a web developer tells you that you can&#8217;t be much of an SEO if you don&#8217;t write valid code then that developer is a clown and should be ignored. If they are just saying that you are not a valid coder then that would be true. From a coder&#8217;s point of view they could go as far as saying that you are a hack, would they be wrong? That said, there are many other reasons to write valid code.  Some of the best SEO gods, gurus, evangelists, provide detailed change requests to web designers and this is often preferred on a valid site so the SEO does not break the valid code. Maybe SEO specialists should inform the client that there is such a thing as validation and let them decide. It&#8217;s similar to an auto mechanic letting the customer decide if they want a factory replacement part or an aftermarket part, is it worth the extra money? Determining that invalid pages are ranked high for certain terms does not tell the complete story but it does tell most of the story. What if a search bot reaches a certain point on a page that is so invalid it stops parsing? At that point the rest of your content would be ignored. What if the next algo revision applies more weight to valid code or is modified so that it halts when a missing end tag is encountered (is Bing already doing this)? You would have partial page results in the index which means you have wasted copy.  More important is the fact that invalid code might not render properly on the next update to your audience&#8217;s preferred browser. At some point the invalid code will probably rear its ugly head and then you will need to pay the piper to write valid code, or at least new code, so why not let the coders get paid for what they do?</p>
<p>We could argue that having a shade tree mechanic use bailing wire to fix a dragging muffler will allow you to use the car again but for how long? Yes it will cost more money to order the new muffler hanger and have a muffler shop install it properly but when you hit that big speed bump at the grocery store which one do you think will hold up? At that point did it really cost more money to have it done right?</p>
<p>I agree if you charge someone to do SEO work and you don&#8217;t write valid code then you aren&#8217;t ripping them off. What if you are upfront and tell them, directly, I am going to make the changes using invalid code, will they care? Should they have a choice or is OK to leave them in the dark since it is to your advantage?</p>
<p>One point Tim implied that I disagree with is that it&#8217;s more expensive to work on valid sites. It is much easier to work on a properly designed CSS and XHTML site than a hacked, table infested, monstrosity. We charge a lot more, well actually, we usually require a complete redesign before we start working on a hacked site but this is strictly related to design work, not SEO. Let me repeat here that I agree that validation has little to do with SEO if anything. I say if anything because we don&#8217;t know if any search engines pay greater weight to valid code and there can be a case made for a parser getting stuck or stopping after a bad or missing tag. Maybe not Google but can we guarantee this won&#8217;t happen with any search engine?</p>
<p>I give the thumbs up to valid code because without validation then you have to set some other standard for when the code is acceptable. It would be much more difficult to create a list of what code is bad or invalid but acceptable. Why not follow the standards that are used to design every web browser?</p>
<p>I also read &#8220;<a href="http://www.seobook.com/source-code-validation-common-sense">source code validation common sense</a>&#8221; over at SEOBook by Aaron Wall. Wow! He really goes off and I don&#8217;t blame him but I have never personally heard a good web designer that is proud of his ability and trade claim that validation is an integral part of SEO work. I say ignore those monkeys but let the design experts maintain their status of elite, or cream of the crop, by writing valid code and proving they are at the top of their game just as you are at the top of yours. Here are some of the <a href="http://validator.w3.org/docs/why.html">top reasons to validate</a>.</p>
<p>added: I would be considered a hack when it comes to XHTML and CSS. If I perform onpage SEO I check to see if the client site is valid. If it is then I make sure it&#8217;s valid when I finish. Often I find errors that I have caused and then I have to employ someone from our design team to fix it. I have been known to render this site invalid just by blogging <img src='http://www.bliznet.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/seo-and-validation/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>More Random Web Design Tips</title>
		<link>http://www.bliznet.com/more-random-web-design-tips/</link>
		<comments>http://www.bliznet.com/more-random-web-design-tips/#comments</comments>
		<pubDate>Fri, 05 Jun 2009 19:14:03 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=167</guid>
		<description><![CDATA[How to write page-specific CSS as necessary without creating an extra stylesheet.]]></description>
			<content:encoded><![CDATA[<h3>Body Element Classes</h3>
<p>One thing I&#8217;ve started doing somewhat recently is adding a unique class name to the <code>body</code> element of each page. This allows me to write page-specific CSS as necessary without creating an extra stylesheet. Ideally, there should be styles for common elements that make up the site, rather than style for each page, but this can&#8217;t always be avoided. One case could be that a particular page needs to have a slightly different layout than the rest of the site. <code>Body</code> element class to the rescue!</p>
<h3>Internet Explorer 6</h3>
<p>We all know Internet Explorer 6 is a regular pain in the neck, right? Fortunately, it&#8217;s easy to add IE6-specific style with this selector:<br />
<code>* html [additional selectors...]</code></p>
<p>For example, the style <code>* html p { font-weight: bold; }</code> makes all paragraphs bold <em>only in Internet Explorer 6</em>.  It&#8217;s valid, but no other major browser will apply it. This is useful because sometimes the style needed to make things in IE6 look one way is <em>drastically</em> different than what is needed to make it look the same in all the other browsers. A simpler solution, though, is to tell your client to upgrade his 8-year-old browser. <img src='http://www.bliznet.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<h3>&#8220;Navbars&#8221;</h3>
<p>A site typically has a &#8220;bar&#8221; of navigational links. Vertically laid out navigation is easy to create and append additional links later. Horizontal navigation is sometimes desired instead, but it&#8217;s not always as trivial to append and can be a little trickier to achieve.</p>
<p>This tip will be focused on horizontal navigation. First, you should most definitely use unordered lists (the <code>ul</code> element) to organize your navigation links whether you&#8217;re using vertical, horizontal, upside-down, or anything-else-you-can-think of navigation. (See the W3&#8242;s excellent <a onclick="return OpenOffSite(this)" href="http://www.w3.org/QA/Tips/unordered-lists">webmaster tips</a> for more on unordered lists and their uses.) Once you&#8217;ve marked up your navigational links, jump over to the stylesheet and add a <code>display: inline;</code> line to your navigation&#8217;s <code>li</code> elements. Now take a step back and behold your now-horizontal navigational links!</p>
<p>If you find you need to set the width and height of your links, just set the display type of the <code>a</code> elements to <code>inline-block</code>, which I was surprised to find out was actually supported in Internet Explorer 6! Once you&#8217;ve set that, your links will behave like block-level elements as far as styling goes, but they will remain positioned inline. <em>Sweet!</em></p>
<p>Well, that&#8217;s all for now. Make sure to check back occasionally for more random web tips from your Uncle Kyle!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/more-random-web-design-tips/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

