<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" version="2.0">

<channel>
	<title>Phrappe</title>
	
	<link>http://phrappe.com</link>
	<description>ice-chilled, instant web tips</description>
	<lastBuildDate>Wed, 22 May 2013 07:17:10 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/phrappe" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="phrappe" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>jQuery element’s tag name</title>
		<link>http://phrappe.com/javascript/jquery-elements-tag-name/</link>
		<comments>http://phrappe.com/javascript/jquery-elements-tag-name/#comments</comments>
		<pubDate>Wed, 22 May 2013 07:17:10 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[javascript]]></category>
		<category><![CDATA[element]]></category>
		<category><![CDATA[jquery]]></category>
		<category><![CDATA[prop()]]></category>
		<category><![CDATA[tag]]></category>
		<category><![CDATA[tagname]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=497</guid>
		<description><![CDATA[Getting the selected element&#8217;s tag name is very easy in jQuery. Just use the below code. Keep in mind that by default the returned tag&#8217;s name is capitalized so if you want it lowercase you&#8217;ll need this :]]></description>
				<content:encoded><![CDATA[<p>Getting the selected element&#8217;s tag name is very easy in jQuery. Just use the below code.</p>
<p><script src="https://gist.github.com/tsevdos/5538859.js"></script></p>
<p>Keep in mind that by default the returned tag&#8217;s name is capitalized so if you want it lowercase you&#8217;ll need this :</p>
<p><script src="https://gist.github.com/tsevdos/5538862.js"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/javascript/jquery-elements-tag-name/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>jPrefetch jQuery plugin</title>
		<link>http://phrappe.com/javascript/jprefetch-jquery-plugin/</link>
		<comments>http://phrappe.com/javascript/jprefetch-jquery-plugin/#comments</comments>
		<pubDate>Tue, 14 May 2013 07:27:03 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[javascript]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[jPrefetch]]></category>
		<category><![CDATA[jquery]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[prefetching]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=500</guid>
		<description><![CDATA[I just released jPrefetch a nice little jQuery plugin that makes HTML5 prefetching a bit easier. You can very easily use it at your current solution (static website or even CMS), just by including it and adding data-prefetch="true" to the link that you want to prefetch. You can also pass a url (string) in order to start [...]]]></description>
				<content:encoded><![CDATA[<p>I just released <a title="jPrefetch" href="https://github.com/tsevdos/jPrefetch" target="_blank">jPrefetch</a> a nice little jQuery plugin that makes <a title="HTML5 Prefetching" href="http://phrappe.com/markup/html5-prefetching/" target="_blank">HTML5 prefetching</a> a bit easier. You can very easily use it at your current solution (static website or even CMS), just by including it and adding <code>data-prefetch="true"</code> to the link that you want to prefetch. You can also pass a url (string) in order to start prefetching the provided url, in case you are loading a page that doesn&#8217;t have any link with the data-prefetch attribute. <a title="jPrefetch" href="https://github.com/tsevdos/jPrefetch" target="_blank">jPrefetch</a> will take care all the rest, and start adding the necessary markup (metatags) in order to allow prefetching in supported browsers (tested in Chrome and Firefox). As you can see, the use of it is very easy and elegant. The plugin was mainly inspired by these two excellent articles, <a title="Mastering HTML5 Prefetching" href="http://www.catswhocode.com/blog/mastering-html5-prefetching">Mastering HTML5 Prefetching</a> and <a title="Link Prefetching with HTML 5 and jQuery" href="http://gavinmorrice.com/blog/posts/tagged/optimization">Prefetching with HTML 5 and jQuery</a>.</p>
<p>Feel free to fork it, use it, whatever <img src='http://phrappe.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/javascript/jprefetch-jquery-plugin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Base tag : Learn how to use it</title>
		<link>http://phrappe.com/markup/base-tag-learn-how-to-use-it/</link>
		<comments>http://phrappe.com/markup/base-tag-learn-how-to-use-it/#comments</comments>
		<pubDate>Wed, 08 May 2013 07:45:44 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[markup]]></category>
		<category><![CDATA[base]]></category>
		<category><![CDATA[tag]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=505</guid>
		<description><![CDATA[Every now and then a friend/colleague of mine asks me to have a look at his latest masterpiece (aka site). In many cases the second request is to have a look at why a specific client side feature is not working. Most of the time, I&#8217;m given a URL of the live version of the site [...]]]></description>
				<content:encoded><![CDATA[<p>Every now and then a friend/colleague of mine asks me to have a look at his latest masterpiece (aka site). In many cases the second request is to have a look at why a specific client side feature is not working. Most of the time, I&#8217;m given a URL of the live version of the site that uses many internal and external resources (css files, javascript files etc). As you can imagine, it&#8217;s super time-consuming to recreate the online page locally to start working on it (downloading and linking all these files).</p>
<p>But don&#8217;t worry, the <code>base</code> tag can save us from this hard task, and help up recreate the online page locally within two simple steps.</p>
<ol>
<li>Copy and paste the markup from the online page in a local file (.html)</li>
<li>Use the <code>base</code> tag to link all the dependencies/resources (you must place it into the <code>head</code> section of the page) to that html file</li>
</ol>
<p><script src="https://gist.github.com/tsevdos/5538872.js"></script></p>
<p>You&#8217;ll end up with a fully functional web-page that uses exactly all the online resources. Now you can either start adding your code to it, or simply download specific files that need re-factoring. Easy and clean, don&#8217;t you think?</p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/markup/base-tag-learn-how-to-use-it/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Autocompletion with HTML5 datalists</title>
		<link>http://phrappe.com/markup/autocompletion-with-html5-datalists/</link>
		<comments>http://phrappe.com/markup/autocompletion-with-html5-datalists/#comments</comments>
		<pubDate>Tue, 23 Apr 2013 07:25:50 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[markup]]></category>
		<category><![CDATA[autocomplete]]></category>
		<category><![CDATA[datalist]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[input]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=474</guid>
		<description><![CDATA[We have all used (and most of us built) an autocomplete input element. There are thousands of plugins/widgets out there, although below I&#8217;m demonstrating the easiest, more semantic and HTML5 way to build it without using Javascript! Just put a normal input element and connect it with the new datalist element by using the list [...]]]></description>
				<content:encoded><![CDATA[<p>We have all used (and most of us built) an autocomplete input element. There are <a title="jQueryUI Autocomplete" href="http://jqueryui.com/autocomplete/">thousands</a> <a title="Ajax autocomplete for jQuery" href="http://www.devbridge.com/projects/autocomplete/jquery/">of plugins/widgets</a> <a title="jQuery plugin: Autocomplete" href="http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/">out there</a>, although below I&#8217;m demonstrating the easiest, more semantic and HTML5 way to build it <strong>without</strong> using Javascript! Just put a normal input element and  connect it with the new datalist element by using the <code>list</code> attribute. That&#8217;s it! You&#8217;re semantically correct, HTML5 autocomplete input is ready!</p>
<p><script src="https://gist.github.com/tsevdos/5441466.js"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/markup/autocompletion-with-html5-datalists/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTML5 Prefetching</title>
		<link>http://phrappe.com/markup/html5-prefetching/</link>
		<comments>http://phrappe.com/markup/html5-prefetching/#comments</comments>
		<pubDate>Tue, 16 Apr 2013 07:21:53 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[markup]]></category>
		<category><![CDATA[attribute]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[prefetch]]></category>
		<category><![CDATA[prefetching]]></category>
		<category><![CDATA[prerender]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=477</guid>
		<description><![CDATA[One of the most interesting, but not widely known features of HTML5 is prefetching. By using it you can start loading pages (or even files) before the user requests them. This can increase your site&#8217;s speed and the user&#8217;s experience! Did I mention that it&#8217;s super easy to implement it? Just put the below code [...]]]></description>
				<content:encoded><![CDATA[<p>One of the most interesting, but not widely known features of HTML5 is prefetching. By using it you can start loading pages (or even files) before the user requests them. This can increase your site&#8217;s speed and the user&#8217;s experience! Did I mention that it&#8217;s super easy to implement it? Just put the below code into the head section of your page:</p>
<p><script type="text/javascript" src="https://gist.github.com/tsevdos/5393996.js"></script></p>
<p>For prefetching a specific file use the same code by pointing directly to the file.</p>
<p><script type="text/javascript" src="https://gist.github.com/tsevdos/5394015.js"></script></p>
<p>The above feature works only on Firefox. If you want to use it in Chrome as well you have to use the &#8220;prerender&#8221; attribute as well:</p>
<p><script src="https://gist.github.com/tsevdos/5394022.js"></script></p>
<p>Browsers that don&#8217;t support prefecthing will simply ignore it (Safari and IE) but sooner or later they will implement it, so you have no reason not to use it asap! Please try not to prefetch everything, it&#8217;s wrong! For more details regarding this neat HTML5 feature have a look at <a title="Mastering HTML5 Prefetching" href="http://www.catswhocode.com/blog/mastering-html5-prefetching">Mastering HTML5 Prefetching</a>, an excellent resource on the topic.</p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/markup/html5-prefetching/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Not so popular HTML5 attributes</title>
		<link>http://phrappe.com/markup/not-so-popular-html5-attributes/</link>
		<comments>http://phrappe.com/markup/not-so-popular-html5-attributes/#comments</comments>
		<pubDate>Mon, 08 Apr 2013 08:05:53 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[markup]]></category>
		<category><![CDATA[attribute]]></category>
		<category><![CDATA[attributes]]></category>
		<category><![CDATA[autofocus]]></category>
		<category><![CDATA[download]]></category>
		<category><![CDATA[hidden]]></category>
		<category><![CDATA[html5]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=469</guid>
		<description><![CDATA[HTML5 offers many new attributes that make our lives easier and our code more semantic. In many cases they even provide functionality that we use to implement with javascript, like the placeholder attribute. I&#8217;m pretty sure you all know the placeholder attribute, but what about the following ones? hidden attribute The hidden attribute, as you [...]]]></description>
				<content:encoded><![CDATA[<p>HTML5 offers many new attributes that make our lives easier and our code more semantic. In many cases they even provide functionality that we use to implement with javascript, like the <a title="The placeholder attribute" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#the-placeholder-attribute">placeholder attribute</a>. I&#8217;m pretty sure you all know the placeholder attribute, but what about the following ones?</p>
<h2>hidden attribute</h2>
<p>The hidden attribute, as you can easily guess, hides the element that is set on. It acts almost identical to style <code>{ display: none; }</code>, but it&#8217;s simpler, cleaner and more semantic (since you are hiding the element directly on DOM rather than style). It is also ridiculously easy to make a fallback on browsers that do not support the specific attribute, just hide it in your styles ( { display: none; } ) or javascript&#8230;</p>
<p><script src="https://gist.github.com/tsevdos/5335061.js"></script></p>
<h2>download attribute</h2>
<p>Do you have downloadable content in your website (like PDF files etc)? If yes then with a little HTML5 attribute you can provide better semantics to the link element, give a better description/title to your file and enforce the browser to download it! Just use the download attribute followed by a string that represents the description/title of your download. Even if your filename is a timestamp or a temp name, the user will download the file,  having as its name the title you used.</p>
<p><script src="https://gist.github.com/tsevdos/5335060.js"></script></p>
<h2>autofocus attribute</h2>
<p>Finally with the autofocus attribute you can autofocus any <code>input</code>, <code>textarea</code> or <code>button</code> you want. Simple as that.</p>
<p><script src="https://gist.github.com/tsevdos/5335056.js"></script></p>
<p>To conclude, whenever possible, try to use the new HTML5 attributes. They will always be more semantically correct and it&#8217;s super easy to implement them. Also, most of them have very simple fallbacks but even if you don&#8217;t provide any, most of the time you won&#8217;t break something, so you don&#8217;t have any excuse.</p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/markup/not-so-popular-html5-attributes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to style a file input element in Firefox</title>
		<link>http://phrappe.com/markup/how-to-style-a-file-input-element-in-firefox/</link>
		<comments>http://phrappe.com/markup/how-to-style-a-file-input-element-in-firefox/#comments</comments>
		<pubDate>Tue, 05 Feb 2013 08:27:58 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[css]]></category>
		<category><![CDATA[markup]]></category>
		<category><![CDATA[element]]></category>
		<category><![CDATA[field]]></category>
		<category><![CDATA[file]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[form]]></category>
		<category><![CDATA[input]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=444</guid>
		<description><![CDATA[Working on a recent project I found out the hard way that Firefox doesn&#8217;t allow you to style a file input element the way you want. I&#8217;m using Chrome for surfing and development, which let&#8217;s you style a file input field without any constraints so I was a bit frustrated when I checked my form in [...]]]></description>
				<content:encoded><![CDATA[<p>Working on a recent project I found out the hard way that Firefox doesn&#8217;t allow you to style a file input element the way you want. I&#8217;m using Chrome for surfing and development, which let&#8217;s you style a file input field without any constraints so I was a bit frustrated when I checked my form in Firefox! With a quick search I discovered that Firefox doesn&#8217;t let you do too much with the file input element. I also discovered some <a title="Styling an input type=&quot;file&quot;" href="http://www.quirksmode.org/dom/inputfile.html">workarounds</a>, but most of them were too complicated for the simple effect I wanted to achieve (to place a background image in the file input field). With a little help from <a title="Resize the input type=“file” browse button in firefox?" href="http://stackoverflow.com/questions/7197835/resize-the-input-type-file-browse-button-in-firefox">stackoverflow</a> <strong>and no javascript</strong> at all, I managed to make it work in Firefox as well as other browsers (see code below).</p>
<p><script src="https://gist.github.com/tsevdos/4713062.js"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/markup/how-to-style-a-file-input-element-in-firefox/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mobile media capture straight to your web form</title>
		<link>http://phrappe.com/markup/mobile-media-capture-straight-to-your-web-form/</link>
		<comments>http://phrappe.com/markup/mobile-media-capture-straight-to-your-web-form/#comments</comments>
		<pubDate>Wed, 23 Jan 2013 08:18:14 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[markup]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[file]]></category>
		<category><![CDATA[form]]></category>
		<category><![CDATA[input]]></category>
		<category><![CDATA[iphone]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=412</guid>
		<description><![CDATA[So, you&#8217;ve just build your latest responsive web design masterpiece and you&#8217;re adding the final touches for the mobile viewport. Suddenly you discover a form where the user must submit a profile image (or video or even audio) in order to continue. Wouldn&#8217;t it be nice to let the user use their phone in order to take [...]]]></description>
				<content:encoded><![CDATA[<p>So, you&#8217;ve just build your latest responsive web design masterpiece and you&#8217;re adding the final touches for the mobile viewport. Suddenly you discover a form where the user must submit a profile <strong>image</strong> (or <strong>video</strong> or even <strong>audio</strong>) in order to continue. Wouldn&#8217;t it be nice to let the user use their phone in order to take a picture (or video or even audio) with it, and at the same time keep the normal fallback of the input file element for desktop browsers? Well you can, just use the below attributes on your <strong>input fields</strong>. Desktop browsers will use them as normal file inputs, while mobile devices will add this extra <strong>native flavor</strong>.</p>
<p><script src="https://gist.github.com/4603033.js"></script></p>
<p>I tested them and they work on iPhone (both on <strong>mobile Safari</strong> and <strong>mobile Chrome</strong>), but they will (probably?) work on any mobile device/browser (android/windows etc.)… Let us know in the comments or via <a title="Tsevdos twitter account" href="https://twitter.com/tsevdos">twitter</a> if they work for you.</p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/markup/mobile-media-capture-straight-to-your-web-form/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Responsive web design and how to be nice to IE</title>
		<link>http://phrappe.com/javascript/responsive-web-design-and-how-to-be-nice-to-ie/</link>
		<comments>http://phrappe.com/javascript/responsive-web-design-and-how-to-be-nice-to-ie/#comments</comments>
		<pubDate>Tue, 15 Jan 2013 07:53:31 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[javascript]]></category>
		<category><![CDATA[markup]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[internet explorer]]></category>
		<category><![CDATA[media queries]]></category>
		<category><![CDATA[responsive web design]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=414</guid>
		<description><![CDATA[Many people believe that Internet Explorer (especially 7 and 8) cannot render correctly responsive web sites. Well the truth is that IE sucks big time (specially versions previous to 9), although the above statement is partially true. With a tiny bit of effort you can make your responsive web site play nicely with IE as [...]]]></description>
				<content:encoded><![CDATA[<p>Many people believe that <strong>Internet Explorer</strong> (especially 7 and 8) cannot render correctly responsive web sites. Well the truth is that IE sucks big time (specially versions previous to 9), although the above statement is partially true. With a tiny bit of effort you can make your responsive web site play nicely with IE as well. Let me tell you how.</p>
<p>The first thing you must do in any case (this tip is not only for <strong>responsive web design</strong>), is to make sure that IE is using the latest rendering engine it supports. We can do this very simply by including the below <strong>metatag</strong>. Finally, if the user has<a title="Google Chrome frame" href="http://www.google.com/chromeframe"> Google Frame</a> (does anyone have it?) we tell IE to use that rendering engine.</p>
<p><script src="https://gist.github.com/4529222.js"></script></p>
<p>Easy so far, the next major problem is that IE8 and below doesn&#8217;t recognise <strong>HTML5 elements</strong>. Again you can include either <a title="html5shiv" href="http://code.google.com/p/html5shiv/">html5shiv</a> or <a title="modernizr" href="http://modernizr.com/">modernizr</a> to fix this. <strong><a title="html5shiv" href="http://code.google.com/p/html5shiv/">Html5shiv</a> </strong>is smaller in filesize and does the job but <strong><a title="modernizr" href="http://modernizr.com/">Modernizr</a></strong> can help you detect browser features (and not only that), the choice is yours.</p>
<p>Finally you can make IE understand <strong>media queries</strong> (a very important part of responsive web design) with the excellent Javascript polyfill <strong><a title="Respond.js" href="https://github.com/scottjehl/Respond">Respond.js</a></strong>. That&#8217;s it, you&#8217;ve made it! With these very simple steps we can be nice to IE and make it treat right our responsive web sites.</p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/javascript/responsive-web-design-and-how-to-be-nice-to-ie/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Call or text from a mobile device using very simple markup</title>
		<link>http://phrappe.com/markup/call-or-text-from-a-mobile-device-using-very-simple-markup/</link>
		<comments>http://phrappe.com/markup/call-or-text-from-a-mobile-device-using-very-simple-markup/#comments</comments>
		<pubDate>Mon, 07 Jan 2013 09:05:31 +0000</pubDate>
		<dc:creator>John Tsevdos</dc:creator>
				<category><![CDATA[markup]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[call]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[ios]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[smartphones]]></category>
		<category><![CDATA[sms]]></category>

		<guid isPermaLink="false">http://phrappe.com/?p=403</guid>
		<description><![CDATA[At my latest presentation (at upNorth web conferce in Greece), people impressed with some very trivial markup that can add many points to your mobile site (and not only) with minimum effort. With the below very easy to implement markup you can make your site interact with the device in order to make phone calls [...]]]></description>
				<content:encoded><![CDATA[<p>At my <a title="Pragmatic Responsive Web Design" href="https://speakerdeck.com/tsevdos/pragmatic-responsive-web-design">latest presentation</a> (at <a title="upNorth web Conference" href="http://www.upnorthconf.gr">upNorth web conferce</a> in Greece), people impressed with some very trivial markup that can add many points to your mobile site (and not only) with minimum effort. With the below very easy to implement markup you can make your site interact with the device in order to make phone calls and/or send sms (I only tested it with iPhone but I believe its working on other devices as well)!</p>
<p><script src="https://gist.github.com/4401142.js"></script></p>
<p>The above enhancements, together with a <a title="How to attach a custom apple iPhone/iPad icon to your website" href="http://phrappe.com/markup/how-to-attach-a-custom-apple-iphoneipad-icon-to-your-website/">custom iOS home screen icon/image</a>, are probably the easiest markup implementations that give to your mobile site/app many more extra points! If you&#8217;ve tested the above example with other devices (android, windows, blackberry, etc.) please confirm that it&#8217;s working (just leave a comment)&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://phrappe.com/markup/call-or-text-from-a-mobile-device-using-very-simple-markup/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
