<?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>Wapple Blog &#187; Google Android</title>
	<atom:link href="http://blog.wapple.net/tag/google-android/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wapple.net</link>
	<description>Addicted to Mobile Web</description>
	<lastBuildDate>Wed, 25 Jan 2012 20:51:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Google Android &#8211; back to the days before CSS</title>
		<link>http://blog.wapple.net/google-android-back-to-the-days-before-css/</link>
		<comments>http://blog.wapple.net/google-android-back-to-the-days-before-css/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 16:23:29 +0000</pubDate>
		<dc:creator>Rich Gubby</dc:creator>
				<category><![CDATA[Mobile Device and Browser Detection]]></category>
		<category><![CDATA[Mobile Web Development]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Exhibit]]></category>
		<category><![CDATA[G1]]></category>
		<category><![CDATA[Google Android]]></category>
		<category><![CDATA[HTC]]></category>
		<category><![CDATA[Mobile Browser Detection]]></category>
		<category><![CDATA[Mobile Phone Detection]]></category>

		<guid isPermaLink="false">http://mobilewebjunkie.com/?p=953</guid>
		<description><![CDATA[Stop Press: The Google Android phone doesn&#8217;t support CSS. Or so the UAProf supplied by HTC for the G1 would have you believe. We&#8217;ve got one in the office and have recently updated its browser software. Only the new user agent profile (an XML file detailing the phone capabilities) now says that it doesn&#8217;t support [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_957" class="wp-caption alignright" style="width: 100px"><img class="size-thumbnail wp-image-957" title="HTC Magic" src="http://mobilewebjunkie.com/wp-content/uploads/2009/07/htc-magic-front-300x300-150x150.jpg" alt="HTC Magic" width="90" height="90" /><p class="wp-caption-text">HTC Magic</p></div>
<p>Stop Press: The Google Android phone doesn&#8217;t support CSS.</p>
<p>Or so the UAProf supplied by HTC for the G1 would have you believe. We&#8217;ve got one in the office and have recently updated its browser software. Only the new user agent profile (an XML file detailing the phone capabilities) now says that it doesn&#8217;t support CSS.</p>
<p>The good news for users of Wapple is that the device profiling system at its heart knows that vendors sometimes make mistakes and takes that into account. Oh, and when HTC update their Uaprof so that it says it supports CSS, it&#8217;ll know and update as appropriate!<span id="more-953"></span></p>
<p>Obviously the Android supports CSS and everyone knows that (apart from HTC by the looks of it). This is a great example of how hard it is to do device profiling yourself and why it&#8217;s so awesome that you&#8217;ve got tools like Architect available to do it for you!</p>
<p>Without these systems in place you&#8217;d be looking at stripped down versions of sites with no style, but instead, you still get great looking Wapple powered mobile sites.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wapple.net/google-android-back-to-the-days-before-css/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<custom_fields><aktt_notify_twitter>no</aktt_notify_twitter></custom_fields>	</item>
	</channel>
</rss>

