<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Mobile CSS Rendering</title>
	<atom:link href="http://www.thisismobility.com/blog/2007/04/02/mobile-css-rendering/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thisismobility.com/blog/2007/04/02/mobile-css-rendering/</link>
	<description>Ripping mobility from the clutches of telecom</description>
	<pubDate>Thu, 08 Jan 2009 22:41:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Andrea Trasatti</title>
		<link>http://www.thisismobility.com/blog/2007/04/02/mobile-css-rendering/#comment-111786</link>
		<dc:creator>Andrea Trasatti</dc:creator>
		<pubDate>Wed, 25 Apr 2007 09:15:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=307#comment-111786</guid>
		<description>The W3C has started a group recently that is working exactly to produce test suites for mobile browsers. They are working fully in public, you can join the mailing list and comment on anything. They have already done some work about markup and CSS. They are also talking with OMA to see if they can include a test suite for mobile CSS.

Ask for Dom, http://www.w3.org/2005/MWI/Tests/

- Andrea</description>
		<content:encoded><![CDATA[<p>The W3C has started a group recently that is working exactly to produce test suites for mobile browsers. They are working fully in public, you can join the mailing list and comment on anything. They have already done some work about markup and CSS. They are also talking with OMA to see if they can include a test suite for mobile CSS.</p>
<p>Ask for Dom, <a href="http://www.w3.org/2005/MWI/Tests/" rel="nofollow">http://www.w3.org/2005/MWI/Tests/</a></p>
<p>- Andrea</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heidi Pollock</title>
		<link>http://www.thisismobility.com/blog/2007/04/02/mobile-css-rendering/#comment-104926</link>
		<dc:creator>Heidi Pollock</dc:creator>
		<pubDate>Sat, 07 Apr 2007 22:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=307#comment-104926</guid>
		<description>There isn't anything to address the problem you're describing (namely, being able to identify when you've used a CSS property that is poorly supported on a given device).  

It's unlikely that there ever would be an automated test for identifying what CSS properties work on given mobile browser (as opposed to identifying what's valid, which sort of exists, though not really because there isn't much agreement on what constitutes valid Mobile CSS) because it's ultimately something that's only possible to verify with human eyeballs. This is true for PC browsers and why the Acid Test exists (http://www.webstandards.org/action/acid2/)

When I was at Yahoo! I created a Mobile Acid test which, of course, they never officially launched. Luckily, I wrangled a "BSD license" for it so I put it up myself (http://www.jwtmp.com/a). Eventually, I'll edit out the references to Yahoo!, but for now it's a cool, quick way to see what simple CSS and XHTML-MP a mobile browser supports. Opera Mini doesn't do particularly well, though Opera Mobile is pretty good. And almost no mobile browser correctly honors the @media screen syntax to filter out styles meant only for PCs which is a huge pain.

Mobile support for CSS is a total crapshoot.</description>
		<content:encoded><![CDATA[<p>There isn&#8217;t anything to address the problem you&#8217;re describing (namely, being able to identify when you&#8217;ve used a CSS property that is poorly supported on a given device).  </p>
<p>It&#8217;s unlikely that there ever would be an automated test for identifying what CSS properties work on given mobile browser (as opposed to identifying what&#8217;s valid, which sort of exists, though not really because there isn&#8217;t much agreement on what constitutes valid Mobile CSS) because it&#8217;s ultimately something that&#8217;s only possible to verify with human eyeballs. This is true for PC browsers and why the Acid Test exists (http://www.webstandards.org/action/acid2/)</p>
<p>When I was at Yahoo! I created a Mobile Acid test which, of course, they never officially launched. Luckily, I wrangled a &#8220;BSD license&#8221; for it so I put it up myself (http://www.jwtmp.com/a). Eventually, I&#8217;ll edit out the references to Yahoo!, but for now it&#8217;s a cool, quick way to see what simple CSS and XHTML-MP a mobile browser supports. Opera Mini doesn&#8217;t do particularly well, though Opera Mobile is pretty good. And almost no mobile browser correctly honors the @media screen syntax to filter out styles meant only for PCs which is a huge pain.</p>
<p>Mobile support for CSS is a total crapshoot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paschal Nee</title>
		<link>http://www.thisismobility.com/blog/2007/04/02/mobile-css-rendering/#comment-103186</link>
		<dc:creator>Paschal Nee</dc:creator>
		<pubDate>Tue, 03 Apr 2007 08:59:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=307#comment-103186</guid>
		<description>Will this not do what you are looking for?
http://jigsaw.w3.org/css-validator/

There's a mobile option on there, not sure exactly what spec it is validating against.

Or is that what you mean when you mention the "The W3C mobile checker"?</description>
		<content:encoded><![CDATA[<p>Will this not do what you are looking for?<br />
<a href="http://jigsaw.w3.org/css-validator/" rel="nofollow">http://jigsaw.w3.org/css-validator/</a></p>
<p>There&#8217;s a mobile option on there, not sure exactly what spec it is validating against.</p>
<p>Or is that what you mean when you mention the &#8220;The W3C mobile checker&#8221;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
