<?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 Web Development</title>
	<atom:link href="http://www.bliznet.com/tag/web-development/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>The img Element Vs the CSS background-image Property</title>
		<link>http://www.bliznet.com/img-vs-background-image/</link>
		<comments>http://www.bliznet.com/img-vs-background-image/#comments</comments>
		<pubDate>Fri, 13 Feb 2009 22:35:57 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=136</guid>
		<description><![CDATA[Find out when to use the img element or when to use the CSS background-image property.]]></description>
			<content:encoded><![CDATA[<p>Don&#8217;t know when to use the <em>img</em> element or when to use the CSS <em>background-image</em> property? Don&#8217;t fret; there is hope. Read further and all shall be revealed.</p>
<p>The <em>img</em> element is best used for pictures that are completely unrelated to the stylesheet. That is, pictures that would need to display no matter how much the look of the site changes. These would be pictures related to a news article or photos in a gallery.</p>
<p>The CSS <em>background-image</em> property is for images that make up the appearance of the stylesheet. These pictures on one stylesheet would be different or just completely absent on another stylesheet. They don&#8217;t add to the content of the page in any way and are only there to give the page its &#8220;look&#8221;. These image files would be stored in the stylesheet&#8217;s <em>images</em> folder. (See my <a title="Organizing Your CSS Files" href="/organizing-your-css-files/">last post</a> for more on this.)</p>
<p>Just another tip from your uncle Kyle!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/img-vs-background-image/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Organizing Your CSS Files</title>
		<link>http://www.bliznet.com/organizing-your-css-files/</link>
		<comments>http://www.bliznet.com/organizing-your-css-files/#comments</comments>
		<pubDate>Fri, 13 Feb 2009 20:30:41 +0000</pubDate>
		<dc:creator>Kyle Blizzard</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.bliznet.com/?p=133</guid>
		<description><![CDATA[How to keep your styles consolidated and make it easy to use them across multiple websites.]]></description>
			<content:encoded><![CDATA[<p>When I create a web site, I like to organize my stylesheets and images into a specific folder structure. It keeps things tidy and separates presentation files (stylesheets and images) from content files (pages and images related to the content). It also leaves room for additional stylesheet &#8220;themes&#8221; for your site.</p>
<p>Here is an example of this folder structure:</p>
<p><em>/styles/<br />
/styles/default/<br />
/styles/default/images/</em></p>
<p><em>Default</em> in this example would be the name of the &#8220;theme&#8221;. The sites I develop typically do not have multiple themes for the user to pick, so I don&#8217;t usually take the time to give them fancy names. However, if your site utilizes multiple stylesheets that the user could choose from (such as at the <a onclick="return OpenOffSite(this)" href="http://www.csszengarden.com/">CSS Zen Garden</a>), creative names would be helpful.</p>
<p>All stylesheets for the <em>Default</em> theme would be placed in the <em>/styles/default/</em> folder. Likewise, images used by those stylesheets would go in the <em>/styles/default/images/</em> folder.</p>
<p>This method keeps your styles consolidated and makes it easy to use them across multiple sites. All you need to do is copy the folder to the other site; you don&#8217;t need to pick through the <em>images</em> folder and figure out which ones are used by the stylesheet and which ones aren&#8217;t.</p>
<p>Technically, you wouldn&#8217;t even need to copy anything to another site. You could just specify the full URL in the <em>link</em> element or <em>@import</em> rule on the page, but I urge you not to do this. Your visitors may be using security software that sees cross-site references as malicious, thus blocking the stylesheet from downloading or, worse, blocking the entire page.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bliznet.com/organizing-your-css-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

