<?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>These things are far too hard &#187; html</title>
	<atom:link href="http://leadingedgescripts.co.uk/tag/html/feed/" rel="self" type="application/rss+xml" />
	<link>http://leadingedgescripts.co.uk</link>
	<description></description>
	<lastBuildDate>Thu, 24 Feb 2011 13:05:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Proposal for HTML 5?</title>
		<link>http://leadingedgescripts.co.uk/web-development/proposal-for-html-5/</link>
		<comments>http://leadingedgescripts.co.uk/web-development/proposal-for-html-5/#comments</comments>
		<pubDate>Sat, 08 Nov 2008 14:09:33 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[html 5]]></category>

		<guid isPermaLink="false">http://www.leadingedgescripts.co.uk/?p=190</guid>
		<description><![CDATA[As a developer, there are certain things I find a bit frustrating about HTML and PHP programming, and this is one of them. I&#8217;m regularly called upon to build shops, or very simple CMS systems with image upload facilities. This is fine, no complaints about that, but when you&#8217;re creating a CMS with image uploads, [...]]]></description>
			<content:encoded><![CDATA[<p>As a developer, there are certain things I find a bit frustrating about HTML and PHP programming, and this is one of them.</p>
<p>I&#8217;m regularly called upon to build shops, or very simple CMS systems with image upload facilities. This is fine, no complaints about that, but when you&#8217;re creating a CMS with image uploads, you always need to handle what happens when your user doesn&#8217;t upload an image &#8211; or what happens if an image is deleted.</p>
<p>Now I know it&#8217;s trivial to create an if statement to conditionally show an image or not, but it would be even more trivial if we could just add another attribute to X/HTML &lt;img&gt; tags to allow specifying an alternative image if no image is available. I know we already have the alt tag, to show text or help users with screen readers, but how about something like altimg=&#8221;image.gif&#8221; as a new attribute?  Then you could just set it up once and everytime an image tag is loaded without a src=&#8221;" attribute, or the file specified by the src=&#8221;" attribute is missing you have a fallback image.</p>
<p>It would mean marginally less typing for me, potentially saving me from the devastating effects of RSI! It could also result in a slightly better end-user experience abolishing those nasty placeholders in IE (and firefox if you have that setting switched on.</p>
<p>Perhaps this has already been suggested elsewhere, I don&#8217;t know, and to be honest I haven&#8217;t really followed the <a href="http://www.w3.org/html/wg/html5/">HTML 5 development</a> so far, so if this (or something similar) is already in there a) please let me know b) great.</p>
<p>
<!-- Begin Google Adsense code -->
<script type="text/javascript"><!--
google_ad_client = "pub-4904188713812219";
/* 468x60, created 02/11/08 */
google_ad_slot = "9286450703";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
<!-- End Google Adsense code -->
</p>
]]></content:encoded>
			<wfw:commentRss>http://leadingedgescripts.co.uk/web-development/proposal-for-html-5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Centering Web Pages</title>
		<link>http://leadingedgescripts.co.uk/web-development/centering-web-pages/</link>
		<comments>http://leadingedgescripts.co.uk/web-development/centering-web-pages/#comments</comments>
		<pubDate>Sat, 01 Nov 2008 18:28:40 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[center]]></category>
		<category><![CDATA[centering]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[html]]></category>

		<guid isPermaLink="false">http://www.leadingedgescripts.co.uk/wp/?p=52</guid>
		<description><![CDATA[Ever made an amazing CSS website firmly centred on the page, only to find out that it doesn’t work properly? No, of course you haven’t. Well unfortunately I have. With most of the CSS centring techniques I’ve seen, when your visitors resize their browser, or are using 800 x 600 screens, the top of your [...]]]></description>
			<content:encoded><![CDATA[<p>Ever made an amazing CSS website firmly centred on the page, only to find out that it doesn’t work properly? No, of course you haven’t. Well unfortunately I have.</p>
<p>With most of the CSS centring techniques I’ve seen, when your visitors resize their browser, or are using 800 x 600 screens, the top of your website seems to cut–off, or slide underneath the browser controls at the top of the window, and the left–hand side of the screen also slides behind the browsers left most edge!</p>
<p>
<!-- Begin Google Adsense code -->
<script type="text/javascript"><!--
google_ad_client = "pub-4904188713812219";
/* 468x60, created 02/11/08 */
google_ad_slot = "9286450703";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
<!-- End Google Adsense code -->
</p>
<p>Not good! It isn’t very accessible, and it looks very unprofessional. It can lead to a website that looks like this:</p>
<p><img src="http://www.leadingedgescripts.co.uk/images/centrepage.jpg" alt="uncentered page" /></p>
<p>Notice how the logo and the text on the right hand side of the screen are cut–off.</p>
<p>I’m sure you’ll agree that no–one wants this to happen to their website. So obviously a fix is required. Sadly I’ve seen some websites advocating using tables to stop this from happening! Thankfully I can’t remember which ones! That suggestion certainly doesn’t appeal to my (now) fairly well developed sense of the rightness of proper semantic markup and separation of presentation from content.</p>
<p>Well here is a technique using pure CSS that will let you centre your website and stop it sliding behind the top and left edges of the screen on smaller displays / browsers.</p>
<p>It’s not perfect as it adds slight bloat to the code in the form of some extra div tags, but it’s a lot better than any of the alternatives I’ve seen.</p>
<p>I don’t think this technique is unique, but I do hope it helps someone.</p>
<p>This is a fixed width, properly centred CSS layout that doesn’t disappear underneath the top and left edges of your screen.</p>
<p>It is cross browser tested, and is in ‘production use’ on two websites I’ve been involved with; <a href="http://www.fabsinglefriends.com/">www.fabsinglefriends.com</a>and <a href="http://www.gemtrap.com/">www.gemtrap.com</a> so I can easily vouch for it.</p>
<p>I’ve made the simplest most basic version of this page I can, so that you don’t have to worry about stripping out reams of code to figure out how it works.</p>
<p>You’ll notice the empty HTML comment above the doctype declaration, this is needed to put IE into quirks mode.</p>
<p>Anyway have fun with this <a href="http://www.leadingedgescripts.co.uk/fixedwidthproperlycentered.html">fixed width properly centered file</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://leadingedgescripts.co.uk/web-development/centering-web-pages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

