<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://mobiforge.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Testing, dotMobi Compliance</title>
 <link>http://mobiforge.com/Testing/dotMobi-Compliance</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Ready.mobi v2.1.1 is live</title>
 <link>http://mobiforge.com/testing/blog/readymobi-v211-live</link>
 <description>&lt;p&gt;You can probably guess by the version number 2.1.1 (from 2.1), there is nothing ground-breaking in this release. Just a few more bug fixes. In particular we have fixed a bug that caused the use of multiple &lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;geshifilter-text&quot;&gt;&amp;lt;hr/&amp;gt;&lt;/code&gt;&lt;/span&gt; tags in your markup to reduce your overall score.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/blog/readymobi-v211-live&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/blog/readymobi-v211-live#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1093</wfw:commentRss>
 <pubDate>Thu, 19 Jun 2008 08:47:39 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">1093 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Image Resizing</title>
 <link>http://mobiforge.com/testing/story/fixit-image-resizing</link>
 <description>&lt;p&gt;Images such as bitmaps have an intrinsic pixel size. Telling the browser in advance what the size is avoids it having to re-flow the page when it receives it. Resizing images at the server reduces the amount of data transferred and the amount of processing the client has to carry out to scale the image.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-image-resizing&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-image-resizing#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/802</wfw:commentRss>
 <pubDate>Thu, 07 Feb 2008 17:26:09 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">802 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Measures</title>
 <link>http://mobiforge.com/testing/story/fixit-measures</link>
 <description>&lt;p&gt;Avoiding pixel and absolute measures allows the browser to adapt content to fit the display, though there are exceptions to this rule (see below). This test checks for the use of absolulte and pixel measures where relative measures would be more appropriate&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-measures&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-measures#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/797</wfw:commentRss>
 <pubDate>Mon, 04 Feb 2008 17:03:47 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">797 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Tables</title>
 <link>http://mobiforge.com/testing/story/fixit-tables</link>
 <description>&lt;p&gt;This test determines if your page uses tables. Tables do not work well on limited size screens and may result in the user having to scroll horizontally to read them. Putting navigational links into tables may result in the user having both to scroll horizontally and vertically to see possible navigational choices.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-tables&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-tables#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/788</wfw:commentRss>
 <pubDate>Fri, 01 Feb 2008 17:45:21 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">788 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Tables for layout</title>
 <link>http://mobiforge.com/testing/story/fixit-tables-layout</link>
 <description>&lt;p&gt;This test attempts to determines if your page is using tables for layout purposes. Tables should be used to present tabular data, rather than to control the layout of a page. The problems associated with using tables for layout are well documented. In particular, they generally require more markup and take longer to render than acheiving the same with CSS.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-tables-layout&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-tables-layout#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/784</wfw:commentRss>
 <pubDate>Thu, 31 Jan 2008 16:50:07 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">784 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Nested Tables</title>
 <link>http://mobiforge.com/testing/story/fixit-nested-tables</link>
 <description>&lt;p&gt;This test determines if your page make use of nested tables. Mobile devices often cannot display nested tables correctly. When a mobile device is capable of displaying nested tables, the computations required to render the tables can consume lot of CPU and add to the display time for the page. &lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-nested-tables&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-nested-tables#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/779</wfw:commentRss>
 <pubDate>Thu, 24 Jan 2008 16:19:48 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">779 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - External Resources</title>
 <link>http://mobiforge.com/testing/story/fixit-external-resources</link>
 <description>&lt;p&gt;This test determines how many externally linked resources your page relies on. Linked resources include images, stylesheets and other objects. Each externally linked resource requires a separate request across the network. This may add a significant amount to the page load time in the mobile context.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-external-resources&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-external-resources#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/777</wfw:commentRss>
 <pubDate>Wed, 23 Jan 2008 17:34:28 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">777 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - No Frames</title>
 <link>http://mobiforge.com/testing/story/fixit-no-frames</link>
 <description>&lt;p&gt;Frames are not supported on many mobile devices, and using them may have unpredictable results. Frames are also considered as being generally problematic. This test checks that your page does not use frames.&lt;br style=&quot;clear:left&quot; /&gt;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-no-frames&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-no-frames#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/754</wfw:commentRss>
 <pubDate>Fri, 04 Jan 2008 17:36:43 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">754 at http://mobiforge.com</guid>
</item>
<item>
 <title>Announcing ready.mobi v2.0</title>
 <link>http://mobiforge.com/testing/blog/announcing-readymobi-v20</link>
 <description>&lt;p&gt;For those who haven&amp;#39;t seen it yet, we&amp;#39;ve gone live with ready.mobi v2.0 (We were going to call v1.1, but the new features are so cool we figured it was worth bumping up to 2.0). &lt;/p&gt;&lt;p&gt;Version 2.0 rocks. New features include&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/blog/announcing-readymobi-v20&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/blog/announcing-readymobi-v20#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/Running">Running</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/validation">Validation</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/567</wfw:commentRss>
 <pubDate>Tue, 28 Aug 2007 11:49:35 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">567 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Pop up windows</title>
 <link>http://mobiforge.com/testing/story/fixit-pop-windows</link>
 <description>&lt;p&gt;Pop-up windows are not supported on many mobile devices, and using them can have unpredicatable results. This test checks that you are not using pop up windows in your markup.&lt;br style=&quot;clear:left&quot; /&gt;&lt;/p&gt; &lt;p&gt;   &lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-pop-windows&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-pop-windows#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/252</wfw:commentRss>
 <pubDate>Fri, 13 Apr 2007 14:42:34 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">252 at http://mobiforge.com</guid>
</item>
</channel>
</rss>

