<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mission: Impossible &#8211; iPad mini detection for HTML5</title>
	<atom:link href="http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent</link>
	<description>Techniques and best practices for delivering the best experience for each mobile device using HTML5</description>
	<lastBuildDate>Fri, 10 May 2013 15:58:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Kontaktannonse</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-29766</link>
		<dc:creator>Kontaktannonse</dc:creator>
		<pubDate>Sat, 04 May 2013 12:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-29766</guid>
		<description><![CDATA[We wouldn’t have to be smart at all if ancient designers wouldn’t have been that stupid and using pt for font-size …
To have regards on those (imho already broken) sites is breaking sites on any coming device in future. That doesn’t make sense at all.

If cm, in and pt would be a physical unit on handheld devices everything would be fine. And that’s something devs have thought of already back in the 80ies. I think we should respect those devs – not the bad web design of the 90ies.

physical units, please. now!]]></description>
		<content:encoded><![CDATA[<p>We wouldn’t have to be smart at all if ancient designers wouldn’t have been that stupid and using pt for font-size …<br />
To have regards on those (imho already broken) sites is breaking sites on any coming device in future. That doesn’t make sense at all.</p>
<p>If cm, in and pt would be a physical unit on handheld devices everything would be fine. And that’s something devs have thought of already back in the 80ies. I think we should respect those devs – not the bad web design of the 90ies.</p>
<p>physical units, please. now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: firt</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-27326</link>
		<dc:creator>firt</dc:creator>
		<pubDate>Sun, 31 Mar 2013 22:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-27326</guid>
		<description><![CDATA[Sure, your eyes have the same resolution if you use iPad Mini or iPad. But everything looks 19% smaller on a Mini; on some kind of apps detecting that and applying a different font size is necessary.]]></description>
		<content:encoded><![CDATA[<p>Sure, your eyes have the same resolution if you use iPad Mini or iPad. But everything looks 19% smaller on a Mini; on some kind of apps detecting that and applying a different font size is necessary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tecmobeto</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-27315</link>
		<dc:creator>tecmobeto</dc:creator>
		<pubDate>Sun, 31 Mar 2013 21:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-27315</guid>
		<description><![CDATA[Have you asked yourself the question why you need to actually check if it’s an iPad Mini though ?]]></description>
		<content:encoded><![CDATA[<p>Have you asked yourself the question why you need to actually check if it’s an iPad Mini though ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vaggelis Tsikalas</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-23900</link>
		<dc:creator>Vaggelis Tsikalas</dc:creator>
		<pubDate>Tue, 05 Feb 2013 14:56:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-23900</guid>
		<description><![CDATA[My guess is that Apple wouldn&#039;t want you to make exceptions for iPad mini compared to iPad, and nor would I, had I bought one.

The iPad mini is for those with smaller fingers and better eyesight than those who prefer the big iPad. Apple uses the same screen resolution as in the iPad 2 and didn&#039;t bother to change anything in the UI, (thus making everything about 20% smaller) considering it&#039;s not such a big deal for the mini buyer.

The iPad mini user eventually gets used to this zoom level (actually, i&#039;d much prefer to have this zoom level on my big iPad, fitting more info on screen), and it would look awkward to suddenly be presented with something relatively bigger.]]></description>
		<content:encoded><![CDATA[<p>My guess is that Apple wouldn&#8217;t want you to make exceptions for iPad mini compared to iPad, and nor would I, had I bought one.</p>
<p>The iPad mini is for those with smaller fingers and better eyesight than those who prefer the big iPad. Apple uses the same screen resolution as in the iPad 2 and didn&#8217;t bother to change anything in the UI, (thus making everything about 20% smaller) considering it&#8217;s not such a big deal for the mini buyer.</p>
<p>The iPad mini user eventually gets used to this zoom level (actually, i&#8217;d much prefer to have this zoom level on my big iPad, fitting more info on screen), and it would look awkward to suddenly be presented with something relatively bigger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: firt</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-20301</link>
		<dc:creator>firt</dc:creator>
		<pubDate>Wed, 14 Nov 2012 23:05:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-20301</guid>
		<description><![CDATA[Thanks. It seems like a bug because both values are incorrect. The problem is that with 6.1 (in beta now) the bug may be &quot;solved&quot; :S]]></description>
		<content:encoded><![CDATA[<p>Thanks. It seems like a bug because both values are incorrect. The problem is that with 6.1 (in beta now) the bug may be &#8220;solved&#8221; :S</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaspars</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-20244</link>
		<dc:creator>Kaspars</dc:creator>
		<pubDate>Wed, 14 Nov 2012 13:55:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-20244</guid>
		<description><![CDATA[I just discovered that &lt;code&gt;screen.availWidth&lt;/code&gt; and &lt;code&gt;screen.availHeight&lt;/code&gt; are different for iPad Mini and iPad 2.

Here is the blog post: http://konstruktors.com/blog/web-design/4396-detect-ipad-mini-javascript/]]></description>
		<content:encoded><![CDATA[<p>I just discovered that <code>screen.availWidth</code> and <code>screen.availHeight</code> are different for iPad Mini and iPad 2.</p>
<p>Here is the blog post: <a href="http://konstruktors.com/blog/web-design/4396-detect-ipad-mini-javascript/" rel="nofollow">http://konstruktors.com/blog/web-design/4396-detect-ipad-mini-javascript/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Trenkler</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-19948</link>
		<dc:creator>Michael Trenkler</dc:creator>
		<pubDate>Sun, 11 Nov 2012 22:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-19948</guid>
		<description><![CDATA[@Orion
We wouldn&#039;t have to be smart at all if ancient designers wouldn&#039;t have been that stupid and using pt for font-size ...
To have regards on those (imho already broken) sites is breaking sites on any coming device in future. That doesn&#039;t make sense at all.

If cm, in and pt would be a physical unit on handheld devices everything would be fine. And that&#039;s something devs have thought of already back in the 80ies. I think we should respect those devs - not the bad web design of the 90ies.

physical units, please. now!

read: http://smus.com/physical-units/]]></description>
		<content:encoded><![CDATA[<p>@Orion<br />
We wouldn&#8217;t have to be smart at all if ancient designers wouldn&#8217;t have been that stupid and using pt for font-size &#8230;<br />
To have regards on those (imho already broken) sites is breaking sites on any coming device in future. That doesn&#8217;t make sense at all.</p>
<p>If cm, in and pt would be a physical unit on handheld devices everything would be fine. And that&#8217;s something devs have thought of already back in the 80ies. I think we should respect those devs &#8211; not the bad web design of the 90ies.</p>
<p>physical units, please. now!</p>
<p>read: <a href="http://smus.com/physical-units/" rel="nofollow">http://smus.com/physical-units/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Jankord</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-19751</link>
		<dc:creator>Brett Jankord</dc:creator>
		<pubDate>Fri, 09 Nov 2012 22:09:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-19751</guid>
		<description><![CDATA[You could always take a page from Jeffrey Zeldman, and just increase your default font-size for all devices. http://www.zeldman.com/  Simple and easy fix.]]></description>
		<content:encoded><![CDATA[<p>You could always take a page from Jeffrey Zeldman, and just increase your default font-size for all devices. <a href="http://www.zeldman.com/" rel="nofollow">http://www.zeldman.com/</a>  Simple and easy fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Orion</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-19730</link>
		<dc:creator>Orion</dc:creator>
		<pubDate>Fri, 09 Nov 2012 19:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-19730</guid>
		<description><![CDATA[In my experience, web designers try to do too much to &quot;figure out&quot; what machine they&#039;re running on. I often turn my iPhone to landscape to read a website because that increases the size of the text. But some sites that detect orientation will keep the text the same size when you switch to landscape and simply put more words on each line! These same sites will usually disable tap zoom, so you can&#039;t even increase the font size that way.

Why not try to be less &quot;smart&quot; and just put a font scale button on the page. Give the user two sizes to choose from and make both sizes layout really nicely. So I can see text more clearly on my iPad Mini, but get better information density on my larger tablet?

I think by not trying to outsmart the user you&#039;ll get a friendlier result]]></description>
		<content:encoded><![CDATA[<p>In my experience, web designers try to do too much to &#8220;figure out&#8221; what machine they&#8217;re running on. I often turn my iPhone to landscape to read a website because that increases the size of the text. But some sites that detect orientation will keep the text the same size when you switch to landscape and simply put more words on each line! These same sites will usually disable tap zoom, so you can&#8217;t even increase the font size that way.</p>
<p>Why not try to be less &#8220;smart&#8221; and just put a font scale button on the page. Give the user two sizes to choose from and make both sizes layout really nicely. So I can see text more clearly on my iPad Mini, but get better information density on my larger tablet?</p>
<p>I think by not trying to outsmart the user you&#8217;ll get a friendlier result</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward O'Connor</title>
		<link>http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent/comment-page-1#comment-19720</link>
		<dc:creator>Edward O'Connor</dc:creator>
		<pubDate>Fri, 09 Nov 2012 17:58:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobilexweb.com/?p=202#comment-19720</guid>
		<description><![CDATA[Err, the commenting stripped out some essential content. That should read:

CSS resolution units are “physical dots per CSS length“, and CSS lengths are in terms of CSS pixels, not device pixels.]]></description>
		<content:encoded><![CDATA[<p>Err, the commenting stripped out some essential content. That should read:</p>
<p>CSS resolution units are “physical dots per CSS length“, and CSS lengths are in terms of CSS pixels, not device pixels.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
