<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jtyost2)</title>
    <link>https://pinboard.in/u:jtyost2/public/</link>
    <description>recent bookmarks from jtyost2</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://bradfrost.com/blog/post/you-probably-dont-need-input-typenumber/"/>
	<rdf:li rdf:resource="https://cloudfour.com/thinks/see-no-evil-hidden-content-and-accessibility/"/>
	<rdf:li rdf:resource="https://css-tricks.com/downsides-of-smooth-scrolling/"/>
	<rdf:li rdf:resource="http://css-tricks.com/redirect-web-page/"/>
	<rdf:li rdf:resource="http://css-tricks.com/scroll-fix-content/"/>
	<rdf:li rdf:resource="http://www.smashingmagazine.com/2014/10/21/providing-a-native-experience-with-web-technologies/"/>
	<rdf:li rdf:resource="http://alistapart.com/article/one-step-ahead-improving-performance-with-prebrowsing"/>
	<rdf:li rdf:resource="http://realfavicongenerator.net/"/>
	<rdf:li rdf:resource="http://techblog.netflix.com/2014/06/html5-video-in-safari-on-os-x-yosemite.html"/>
	<rdf:li rdf:resource="https://medium.com/medium-eng/122d8a40e480"/>
	<rdf:li rdf:resource="http://css-tricks.com/line-menu-icon-menu/"/>
	<rdf:li rdf:resource="http://coding.smashingmagazine.com/2013/11/13/laying-the-groundwork-for-extensibility/"/>
	<rdf:li rdf:resource="https://www.eff.org/deeplinks/2013/10/lowering-your-standards"/>
	<rdf:li rdf:resource="http://www.sitepoint.com/html5-geolocation/"/>
	<rdf:li rdf:resource="http://parall.ax/products/jspdf"/>
	<rdf:li rdf:resource="http://torquemag.io/what-is-wordpress-lacking-a-template-language/"/>
	<rdf:li rdf:resource="http://james.padolsey.com/general/semantic-html-is-dying/"/>
	<rdf:li rdf:resource="http://css-tricks.com/just-one-of-those-weird-things-about-css-background-on-body/"/>
	<rdf:li rdf:resource="https://github.com/javve/list"/>
	<rdf:li rdf:resource="https://www.eff.org/press/releases/eff-makes-formal-objection-drm-html5"/>
	<rdf:li rdf:resource="https://github.com/josephschmitt/Clamp.js"/>
	<rdf:li rdf:resource="https://37signals.com/svn/posts/3511-recent-versions-of-google-chrome-on-os-x"/>
	<rdf:li rdf:resource="http://davidwalsh.name/download-attribute"/>
	<rdf:li rdf:resource="http://css-tricks.com/magic-numbers-in-css/"/>
	<rdf:li rdf:resource="http://tjvantoll.com/2013/04/15/list-of-pseudo-elements-to-style-form-controls/"/>
	<rdf:li rdf:resource="http://techblog.netflix.com/2013/04/html5-video-at-netflix.html"/>
	<rdf:li rdf:resource="http://www.guardian.co.uk/technology/blog/2013/mar/12/tim-berners-lee-drm-cory-doctorow?CMP=twt_fd"/>
	<rdf:li rdf:resource="http://paulirish.com/2013/webkit-for-developers/"/>
	<rdf:li rdf:resource="http://css-tricks.com/mixing-responsive-design-and-mobile-templates/"/>
	<rdf:li rdf:resource="http://www.netmagazine.com/opinions/jeffrey-zeldman-dream-standards-based-web"/>
	<rdf:li rdf:resource="https://github.com/aFarkas/html5shiv"/>
	<rdf:li rdf:resource="http://intridea.github.com/stately/"/>
	<rdf:li rdf:resource="http://www.sencha.com/blog/the-making-of-fastbook-an-html5-love-story/"/>
	<rdf:li rdf:resource="http://incident57.com/codekit/kit.php"/>
	<rdf:li rdf:resource="http://www.campaignmonitor.com/blog/post/3890/adding-audio-to-email-newsletters"/>
	<rdf:li rdf:resource="http://www.w3.org/News/2012"/>
	<rdf:li rdf:resource="https://github.com/docverter/docverter"/>
	<rdf:li rdf:resource="http://maker.github.com/ratchet/"/>
	<rdf:li rdf:resource="http://css-tricks.com/the-facebook-loading-animation-in-css/"/>
	<rdf:li rdf:resource="http://blog.javierusobiaga.com/stop-using-the-viewport-tag-until-you-know-ho"/>
	<rdf:li rdf:resource="http://www.brucelawson.co.uk/2012/on-drm-in-html5/"/>
	<rdf:li rdf:resource="http://www.webmonkey.com/2012/10/mozilla-plans-h-264-video-for-desktop-firefox/"/>
	<rdf:li rdf:resource="http://stopdesign.com/archive/2012/10/11/ten-years-later.html"/>
	<rdf:li rdf:resource="http://codepen.io/joshnh/pen/ohbHl"/>
	<rdf:li rdf:resource="http://www.campaignmonitor.com/blog/post/3780/removing-the-60-character-line-limit-on-plain-text-email"/>
	<rdf:li rdf:resource="http://www.nczonline.net/blog/2012/08/22/the-innovations-of-internet-explorer/"/>
	<rdf:li rdf:resource="http://www.campaignmonitor.com/blog/post/3795/outlook-2013-says-no-to-empty-table-cells"/>
	<rdf:li rdf:resource="https://github.com/arturadib/strapdown"/>
	<rdf:li rdf:resource="http://humblesoftware.com/flotr2/"/>
	<rdf:li rdf:resource="http://css-tricks.com/saving-the-day-with-scoped-css/"/>
	<rdf:li rdf:resource="http://www.ryancollins.me/?p=1041"/>
	<rdf:li rdf:resource="http://designshack.net/articles/css/whats-the-deal-with-display-inline-block/"/>
	<rdf:li rdf:resource="https://github.com/darcyclarke/Front-end-Developer-Interview-Questions"/>
	<rdf:li rdf:resource="http://www.frankieroberto.com/responsive_text"/>
	<rdf:li rdf:resource="http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#the-translate-attribute"/>
	<rdf:li rdf:resource="http://dev.w3.org/csswg/css3-hierarchies/"/>
	<rdf:li rdf:resource="http://davidwalsh.name/prevent-form-autocomplete"/>
	<rdf:li rdf:resource="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/034506.html"/>
	<rdf:li rdf:resource="https://github.com/mathiasbynens/jquery-placeholder"/>
	<rdf:li rdf:resource="http://html5doctor.com/the-output-element/"/>
	<rdf:li rdf:resource="https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Browser-Polyfills"/>
	<rdf:li rdf:resource="https://github.com/necolas/css3-social-signin-buttons"/>
	<rdf:li rdf:resource="https://github.com/DataZombies/DBi"/>
	<rdf:li rdf:resource="https://github.com/TapQuo/Lungo.js"/>
	<rdf:li rdf:resource="https://github.com/dnewcome/Donatello"/>
	<rdf:li rdf:resource="https://github.com/zynga/scroller"/>
	<rdf:li rdf:resource="http://octopress.org/"/>
	<rdf:li rdf:resource="http://leaverou.me/2011/09/pure-css3-typing-animation-with-steps/"/>
	<rdf:li rdf:resource="http://arstechnica.com/open-source/news/2011/09/reflecting-on-chrome-as-browser-hits-third-birthday.ars"/>
	<rdf:li rdf:resource="https://github.com/imakewebthings/deck.js"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://bradfrost.com/blog/post/you-probably-dont-need-input-typenumber/">
    <title>You probably don't need input type=“number”</title>
    <dc:date>2019-03-29T23:58:45+00:00</dc:date>
    <link>http://bradfrost.com/blog/post/you-probably-dont-need-input-typenumber/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Time and time again, it seems like reaching for input type="number" is a good idea, but it almost always isn’t. While input type="number triggers numeric keyboards on touchscreens leading to better mobile UX, that can also be accomplished by configuring the pattern attribute in a certain way (Zach Leatherman has a great deep dive post into all of this). I’ll also say that incrementing/decrementing a number with a mouse’s scroll wheel (especially the crappy Magic Mouse) is a lousy pattern even for proper numeric input (“Dammit! I wanted to buy two pairs of socks, not 39.”)

]]></description>
<dc:subject>webdevelopment usability html software webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:150d7f369740/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cloudfour.com/thinks/see-no-evil-hidden-content-and-accessibility/">
    <title>See No Evil: Hidden Content and Accessibility</title>
    <dc:date>2019-03-16T18:24:33+00:00</dc:date>
    <link>https://cloudfour.com/thinks/see-no-evil-hidden-content-and-accessibility/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[When I first started learning web development I thought hiding content was simple: slap display: none; onto your hidden element and call it a day. Since then I’ve learned about screen readers, ARIA attributes, the HTML5 hidden attribute, and more!

It’s important to ensure our websites are accessible to everyone, regardless of whether or not they use a screen reader, but with this myriad of options, how do we know when to use what?

There are four main scenarios where you may wish to hide content:
1. Hiding content for everyone, regardless of whether they use a screen reader
2. Hiding content for screen readers while showing it to other users
3. Showing additional content for screen readers while hiding it from other users
4. Hiding content at specific screen sizes

Let’s dive deeper into each of those scenarios to learn how to handle them.]]></description>
<dc:subject>design software webdesign webdevelopment accessibility css html</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ee7eca63c2b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://css-tricks.com/downsides-of-smooth-scrolling/">
    <title>Downsides of Smooth Scrolling | CSS-Tricks</title>
    <dc:date>2019-03-11T21:50:33+00:00</dc:date>
    <link>https://css-tricks.com/downsides-of-smooth-scrolling/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[I can see not being able to adjust timing being a downside, but that wasn't what made me ditch smooth scrolling. The thing that seemed to frustrate a ton of people was on-page search. It's one thing to click a link and get zoomed to some header (that feels sorta good) but it's another when you're trying to quickly pop through matches when you do a Find on the page. People found the scrolling between matches slow and frustrating. I agreed.]]></description>
<dc:subject>css software html javascript webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:90cc763ca070/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/redirect-web-page/">
    <title>How to Redirect a Web Page | CSS-Tricks</title>
    <dc:date>2014-12-26T02:34:51+00:00</dc:date>
    <link>http://css-tricks.com/redirect-web-page/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A redirect is when a web page is visited at a certain URL, it changes to a different URL. For instance, a person visits "website.com/page-a" in their browser and they are redirected to "website.com/page-b" instead. This is very useful if we want to redirect a certain page to a new location, change the URL structure of a site, remove the "www." portion of the URL, or even redirect users to another website entirely (just to name a few).

Let's say we've just moved our website and we want to shut down the old one. However we don't want all those pages from the old site to give a dreaded 404 Not Found. What we need is for those old links to redirect to the same content on our new site.

Here's our example: we want old-website.com/blog/post to redirect to new-website.com/blog/post, along with all the other posts that use that same URL format. Also it would be nice if our redirects would report to search engines that this change is permanent so they should update accordingly.

So how do we that? Well, before we start we need to learn a little about HTTP.]]></description>
<dc:subject>webdevelopment webdesign software php javascript html http apache nginx</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:3737c2bd89bb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:nginx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/scroll-fix-content/">
    <title>Scroll-Then-Fix Content | CSS-Tricks</title>
    <dc:date>2014-11-06T01:21:15+00:00</dc:date>
    <link>http://css-tricks.com/scroll-fix-content/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Like most good tricks, there isn't much to it. All we do is think of (and design for) the two different possible states:

Search bar in its scrollable position
Search bar in its fixed header position
We toggle between them simply by changing a class name. There is no trickery with having two search forms that reveal themselves in different scenarios. That's good, as we don't want to smurf around with keeping those in sync. Much easier to just move a single one around.]]></description>
<dc:subject>design webdesign webdevelopment css html javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ce02610bc8fa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.smashingmagazine.com/2014/10/21/providing-a-native-experience-with-web-technologies/">
    <title>Hybrid Mobile Apps: Providing A Native Experience With Web Technologies | Smashing Magazine</title>
    <dc:date>2014-10-22T03:01:46+00:00</dc:date>
    <link>http://www.smashingmagazine.com/2014/10/21/providing-a-native-experience-with-web-technologies/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[According to a recent report, HTML is the most widely used language for mobile app developers. The main reasons among developers for selecting web technologies are cross-platform portability of code and the low cost of development. We’ve also heard that hybrid apps tend to be sluggish and poorly designed. Let’s prove whether it’s possible to deliver the native look and feel that we’re used to.]]></description>
<dc:subject>html html5 webdesign mobile software technology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e90a185728c8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alistapart.com/article/one-step-ahead-improving-performance-with-prebrowsing">
    <title>One Step Ahead: Improving Performance with Prebrowsing · An A List Apart Article</title>
    <dc:date>2014-10-15T04:53:17+00:00</dc:date>
    <link>http://alistapart.com/article/one-step-ahead-improving-performance-with-prebrowsing</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[But we can still do more. If we want faster outcomes, we have to think differently. What if, instead of leaving our users to stare at a spinning wheel, waiting for content to be delivered, we could predict where they wanted to go next? What if we could have that content ready for them before they even ask for it?

We tend to see the web as a reactive model, where every action causes a reaction. Users click, then we take them to a new page. They click again, and we open another page. But we can do better. We can be proactive with prebrowsing.]]></description>
<dc:subject>internet programming software development webdevelopment performance prefetch hardware prebrowsing html optimization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:993573f241be/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:prefetch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:prebrowsing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:optimization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://realfavicongenerator.net/">
    <title>Favicon Generator - Generate favicon pictures and HTML</title>
    <dc:date>2014-08-24T07:23:46+00:00</dc:date>
    <link>http://realfavicongenerator.net/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Generate the favicon pictures and HTML code that work on all major browsers and platforms]]></description>
<dc:subject>favicon design webdesign webdevelopment html software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e929cce21f3c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:favicon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://techblog.netflix.com/2014/06/html5-video-in-safari-on-os-x-yosemite.html">
    <title>The Netflix Tech Blog: HTML5 Video in Safari on OS X Yosemite</title>
    <dc:date>2014-06-04T06:38:08+00:00</dc:date>
    <link>http://techblog.netflix.com/2014/06/html5-video-in-safari-on-os-x-yosemite.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[We're excited to announce that Netflix streaming in HTML5 video is now available in Safari on OS X Yosemite! We've been working closely with Apple to implement the Premium Video Extensions in Safari, which allow playback of premium video content in the browser without the use of plugins. If you're in Apple's Mac Developer Program, or soon the OS X Beta Program, you can install the beta version of OS X Yosemite. With the OS X Yosemite Beta on a modern Mac, you can visit Netflix.com today in Safari and watch your favorite movies and TV shows using HTML5 video without the need to install any plugins. 

We're especially excited that Apple implemented the Media Source Extensions (MSE) using their highly optimized video pipeline on OS X. This lets you watch Netflix in buttery smooth 1080p without hogging your CPU or draining your battery. In fact, this allows you to get up to 2 hours longer battery life on a MacBook Air streaming Netflix in 1080p - that’s enough time for one more movie! 

Apple also implemented the Encrypted Media Extensions (EME) which provides the content protection needed for premium video services like Netflix. 

Finally, Apple implemented the Web Cryptography API (WebCrypto) in Safari, which allows us to encrypt and decrypt communication between our JavaScript application and the Netflix servers. 

The Premium Video Extensions do away with the need for proprietary plugin technologies for streaming video. In addition to Safari on OS X Yosemite, plugin-free playback is also available in IE 11 on Windows 8.1, and we look forward to a time when these APIs are available on all browsers. 

Congratulations to the Apple team for advancing premium video on the web with Yosemite! We’re looking forward to the Yosemite launch this Fall.]]></description>
<dc:subject>html5 html netflix drm safari encryption video</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:a2d8aa6c8213/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:safari"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:video"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/medium-eng/122d8a40e480">
    <title>Why ContentEditable is Terrible — Medium Engineering — Medium</title>
    <dc:date>2014-05-17T21:33:49+00:00</dc:date>
    <link>https://medium.com/medium-eng/122d8a40e480</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[ContentEditable is the native widget for editing rich text in a web browser. It is…sad.

I’m going to try to prove to you, with some hand-wavey math, that the current approach of ContentEditable is broken. This is not because I think math is a persuasive way to make this argument. It actually makes the argument more alienating.

But I do think that text editors lead to lots of fuzzy, ill-defined questions like “What does What-You-See-Is-What-You-Get (WYSIWYG) even mean?” and “What happens when you select this text and hit Enter?” Axiomatic math is the best toolkit I know to take fuzzy, ill-defined questions and sharpen them.

So what does WYSIWYG mean? A good WYSIWYG editor should satisfy the following 3 axioms:

The mapping between DOM content and Visible content should be well-behaved.
The mapping between DOM selection and Visible selection should be well-behaved.
All visible edits should map onto an algebraically closed and complete set of visible content.
First, I’ll explain what each of these 3 axioms mean, and why a good editor should obey these rules. But let’s be clear: they’re axioms. The weakest part of any proof. We’re assuming they’re OK unless we have evidence otherwise.

Second, I’ll show that ContentEditable fails all 3 axioms.

Third, we’ll talk about how new browser features and libraries try to address these issues, and how we handle them in the Medium editor.]]></description>
<dc:subject>html dom design software usability standards mathematics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b5aa41910e72/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:dom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mathematics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/line-menu-icon-menu/">
    <title>Line Menu Icon... That Is A Menu | CSS-Tricks</title>
    <dc:date>2014-02-16T23:33:17+00:00</dc:date>
    <link>http://css-tricks.com/line-menu-icon-menu/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[I had a dumb little idea the other night so I just coded it up (as you do). You know those little icons that have come represent navigation? We've called them Three Line Menu icons around here, but otherwise known as Navicon (clever) or Hamburger (dumb). The point of that icon is that it looks like a little menu, so hopefully it's obvious you click it to reveal a real menu. But what if that icon wasn't an icon at all, but the actual menu, just shrunken?]]></description>
<dc:subject>menu navigation webdesign webdevelopment css html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:83bae1dd4800/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:menu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:navigation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://coding.smashingmagazine.com/2013/11/13/laying-the-groundwork-for-extensibility/">
    <title>Laying The Groundwork For Extensibility | Smashing Coding</title>
    <dc:date>2014-01-02T19:24:20+00:00</dc:date>
    <link>http://coding.smashingmagazine.com/2013/11/13/laying-the-groundwork-for-extensibility/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[In an earlier time, attempting such a sweeping cultural change might have been foolish. Starting at a declarative level was undoubtedly a good idea. However, explaining even a bit of the underlying magic goes a long way: Exposing a DOM tree JavaScript opened new worlds to developers and bolstered the competitiveness of the platform. It also enabled the community to adapt through experimentation and enabled libraries to compete. This allows valuable, popular API ideas to potentially be standardized. The community can do it faster and with less risk than browser vendors and standards organizations can.
The answers aren’t always obvious, but the process of asking “How does that work?” is often more fruitful than it first appears. Details come into focus and missing explanations are uncovered, layer by layer. At each layer, it’s tempting to throw up our collective hands and say “It’s too hard” to explain all the stuff down there. Throw it all out. Start over. At least we won’t make the same mistakes, right?
Perhaps. But we’d also be starting from zero. Zero users, zero developers and zero useful content. The Web is the open, extensible, multi-vendor, universal platform of our lifetime. Small, meaningful changes to the Web can have an outsized impact relative to the effort involved. It’s a straightforward way to do a great deal of good. Encouraging layering, bit by bit, doesn’t mean giving up or “slowing down.” Just the opposite: It’s our only credible hope of making a Web that’s worthy to succeed the Web we have today.]]></description>
<dc:subject>standards html5 html webdevelopment software api w3c</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:de34a823e606/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.eff.org/deeplinks/2013/10/lowering-your-standards">
    <title>Lowering Your Standards: DRM and the Future of the W3C | Electronic Frontier Foundation</title>
    <dc:date>2013-12-26T21:22:46+00:00</dc:date>
    <link>https://www.eff.org/deeplinks/2013/10/lowering-your-standards</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Just five years ago, font companies tried to demand DRM-like standards for embedded Web fonts. These Web typography wars fizzled out without the adoption of these restrictions, but now that such technical restrictions are clearly "in scope," why wouldn't typographers come back with an argument for new limits on what browsers can do?

Indeed, within a few weeks of EME hitting the headlines, a community group within W3C formed around the idea of locking away Web code, so that Web applications could only be executed but not examined online. Static image creators such as photographers are eager for the W3C to help lock down embedded images. Shortly after our Tokyo discussions, another group proposed their new W3C use-case: "protecting" content that had been saved locally from a Web page from being accessed without further restrictions. Meanwhile, publishers have advocated that HTML textual content should have DRM features for many years.

In our conversations with the W3C, we argued that the W3C needed to develop a clearly defined line against the wave of DRM systems it will now be encouraged to adopt.

A Web where you cannot cut and paste text; where your browser can't "Save As..." an image; where the "allowed" uses of saved files are monitored beyond the browser; where JavaScript is sealed away in opaque tombs; and maybe even where we can no longer effectively "View Source" on some sites, is a very different Web from the one we have today. It's a Web where user agents—browsers—must navigate a nest of enforced duties every time they visit a page. It's a place where the next Tim Berners-Lee or Mozilla, if they were building a new browser from scratch, couldn't just look up the details of all the "Web" technologies. They'd have to negotiate and sign compliance agreements with a raft of DRM providers just to be fully standards-compliant and interoperable.

To be clear, we don't think all of these proposals will come to fruition. We appreciate that there's no great hunger for DRM at the W3C. Many W3C participants held their nose to accept even the EME draft, which was carefully drafted to position itself as far away from the taint of DRM as was possible for a standard solely intended to be used for DRM systems.

But the W3C has now accepted "content protection". By discarding the principle that users should be in charge of user agents, as well as the principle that all the information needed to interoperate with a standard should be open to all prospective implementers, they've opened the door for the many rightsholders who would like the same control for themselves.

The W3C is now in an unenviable position. It can either limit its "content protection" efforts to the aims of a privileged few, like Hollywood. Or it can let a thousand "content protection systems" bloom, and allow any rightsholder group to chip away at software interoperability and users' control.

EFF is still a W3C member, and we'll do our best to work with other organizations within and without the consortium to help it fight off the worse consequences of accepting DRM. But it's not easy to defend a king who has already invited its attackers across his moat.

Still, even if the W3C has made the wrong decision, that doesn't mean the Web will. The W3C has parted ways with the wider Web before: in the early 2000s, its choice to promote XHTML (an unpopular and restrictive variant of HTML) as the future led to Mozilla, Apple and Opera forming the independent WHATWG. It was WHATWG's vision of a dynamic, application-oriented Web that won—so decisively, in fact, that the W3C later re-adopted it and made it the W3C's own HTML5 deliverable.

Recently, WHATWG has diplomatically parted with the W3C again. Its "HTML Living Standard" continues to be developed in tandem with the W3C's version of the HTML standard, and does not contain EME or any other such DRM-enabling proposals.

By contrast, W3C has now put its weight behind a restrictive future: let's call it "DRM-HTML". Others have certainly bet against open, interoperable standards and user control before. It's just surprising and disappointing to see the W3C and its Director gamble against the precedent of their own success, as well as the fears and consciences of so many of their colleagues.]]></description>
<dc:subject>drm html5 eff privacy legal copyright w3c standards html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:5686682474f4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:eff"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sitepoint.com/html5-geolocation/">
    <title>HTML5 Geolocation - SitePoint</title>
    <dc:date>2013-09-19T03:29:41+00:00</dc:date>
    <link>http://www.sitepoint.com/html5-geolocation/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The Geolocation API of HTML5 helps in identifying the user’s location, which can be used to provide location specific information or route navigation details to the user.]]></description>
<dc:subject>geolocation api html5 html webdesign webdevelopment software programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:1404bd44ec0f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:geolocation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://parall.ax/products/jspdf">
    <title>jsPDF - HTML5 PDF Generator | Parallax</title>
    <dc:date>2013-08-30T18:21:05+00:00</dc:date>
    <link>http://parall.ax/products/jspdf</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A HTML5 client-side solution for generating PDFs.]]></description>
<dc:subject>pdf library html html5 javascript programming webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:46193335f5b1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://torquemag.io/what-is-wordpress-lacking-a-template-language/">
    <title>What is WordPress Lacking? A Template Language | @thetorquemag</title>
    <dc:date>2013-08-30T18:02:15+00:00</dc:date>
    <link>http://torquemag.io/what-is-wordpress-lacking-a-template-language/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Twig

There’s a lot to love about Twig.

Community

Twig is under active development and serves as the template engine for the Symfony Framework (it’s also maintained by Snyfony’s lead) and serves as the new template language for Drupal 8. Before you “boo” just because it’s Drupal, this is actually a major vote of confidence behind Twig. The more platforms it’s integrated in, the more it will be supported for performance, security, features, etc.

Also, its syntax is based on the Django template language. This isn’t something some dude dreamed up in his garage, it’s got lots of thought and history behind it.

These choices are reflected in the excellent documentation put together by Sensio Labs. They provide great reference and walkthroughs for both designers (who might use Twig in a template) and developers (who might add a special filter or function for a plugin or theme).

Syntax

Twig is simple and consistent. The brace syntax is pretty universal, but Twig’s handling is stellar:

All variables get the double-brace ({{foo}}) syntax, while control structures (includes, conditionals, loops) get brace-percent ({% if foo %}). For introducing filters (filters and functions), Twig promotes a single clear way for template designers to work using the pipe “|”:

It’s easy to write new filters for your plugin or theme (but not too easy) in order to match the functionality you need.

Performance

Fabien Potencier has a very detailed article (from 2009) measuring the (minimal) performance costs on compilation. In my tests, Twig had zero performance impacts on a theme. This is because Twig compiles to PHP.

Moving into WordPress

Turns out there are already a handful of projects dedicated to linking WordPress and Twig. None of them have really caught fire. Here’s the rundown:

AP Twig Bridge

Unfortunately abandoned, this project (last updated in 2011) was pretty much a direct porting of Twig into WordPress. I think it failed to catch on because it essentially trades one hat for another. Many of the complaints about WordPress themes survive — just translated into Twig:

As you can see, it’s basically just moving WP functions into Twig.

WordPress MTV

This project also got off to a really promising start (written by the awesome Newsapps team at the Chicago Tribune). MTV has been around for a while (since 2011) but has some more recent activity (updated on GitHub just about a week ago).

MTV provides tons of power, which is where I got tripped up a bit. It’s an entire framework to write your theme. This may be exactly what some people are looking for (indeed I can think of at least one project from the past I wished I had used with this). But what scares me a bit is how total this solution is (from the GH page: “This plugin hijacks and takes over how WordPress handles URLs”)

My Solution: Timber

I’ve been working on my own “Goldilocks” solution for the last few months called “Timber.” My goal is to combine the great syntax of Twig (which is also shared in MTV), but make the PHP side as simple as possible. This is how small a theme’s single.php can be with Timber:

 

… and then the corresponding .twig file (which is just html with Twig variables and components)

We put Timber into production on a major project for Random House. Since then, we’ve used it on every single WordPress project to cut down on development time, reduce debugging, and confidently turn over better code to the client for them to manage.

It’s a plugin that enables us to use Twig in themes. “Enables” is the key word: it can be implemented where it makes most sense for the project as opposed to all-or-nothing.

Because Twig clearly exposes the HTML, this has made it much easier to do responsive design (everything we do at Upstatement is now responsive).

A template language won’t work for every scenario. But when you have a mix of people working together on a project in both the HTML/CSS (front-end) and PHP (back-end) worlds; it causes way less conflicts in Git. The template syntax also empowers designers to take ownership of the theme even if they don’t know much PHP.

If democratizing publishing is WordPress’s guiding principle, making it easier for semi-technical people to interact and customize their theme seems like a great next step]]></description>
<dc:subject>wordpress smarty template programming mustache html webdevelopment twig</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:7f2751ed9378/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:wordpress"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:smarty"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:template"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mustache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:twig"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://james.padolsey.com/general/semantic-html-is-dying/">
    <title>Semantic HTML is dying – James Padolsey</title>
    <dc:date>2013-08-04T19:19:11+00:00</dc:date>
    <link>http://james.padolsey.com/general/semantic-html-is-dying/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[We have all this semantically rich information (like cinema timings/locations for example) curated over countless man hours and it’s all just sitting on private database servers. The exposed representation, as you can see above, is not enriched, not semantic, and not really usable.
Ok, semantically-poor HTML is still usable — I just have to implement a generic date-parser, a natural-language processor, a domain specific location parser, and maybe I can throw in some neural networking too, huh?
All that effort developing software that can parse and make sense of data that should have been semantic to begin with. What a waste of time & effort.
I know this plea is fruitless though. People want their magical web with embedded tweets and Instagram photos. They couldn’t care less about semantic enrichment.
But we should care. We understand the tenets of the web; the mere fact that via HTTP You or A Server In Timbuktu can request a resource and get back a corresponding representation in HTML. That universality is squandered every time we write crap HTML or choose not to progressively enhance.]]></description>
<dc:subject>html information technology software SemanticHTML</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b866345d7cd3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:SemanticHTML"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/just-one-of-those-weird-things-about-css-background-on-body/">
    <title>Just One of Those Weird Things About CSS: Background on &lt;body&gt; | CSS-Tricks</title>
    <dc:date>2013-07-20T21:27:33+00:00</dc:date>
    <link>http://css-tricks.com/just-one-of-those-weird-things-about-css-background-on-body/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[In the absence of a background on the html element, the body background will cover the page. If there is a background on the html element, the body background behaves just like any other element.

Somewhere along the line, a background-color got set on the html element.

Perhaps you're using normalize.css 2.1.1, which included setting the background to white on the html element to "Prevent system color scheme's background color being used in Firefox, IE, and Opera." This has since been reverted, presumably because it caused this issue too widely.

To "fix" it, just remove the background on the html element, or move whatever you want to "flood" always to the html element as its behavior is consistant.]]></description>
<dc:subject>html css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:8b9b79f8db65/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/javve/list">
    <title>javve/list · GitHub</title>
    <dc:date>2013-06-02T01:36:53+00:00</dc:date>
    <link>https://github.com/javve/list</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Do you want a 3 KB (gzipped&minified) cross-browser native JavaScript that makes your plain HTML lists super flexible, searchable, sortable and filterable? Yeah! Do you also want the possibility to add, edit and remove items by dead simple templating? Hell yeah!]]></description>
<dc:subject>html javascript library</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:50926e668fd8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:library"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.eff.org/press/releases/eff-makes-formal-objection-drm-html5">
    <title>EFF Makes Formal Objection to DRM in HTML5 | Electronic Frontier Foundation</title>
    <dc:date>2013-05-30T02:49:58+00:00</dc:date>
    <link>https://www.eff.org/press/releases/eff-makes-formal-objection-drm-html5</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Today the Electronic Frontier Foundation (EFF) filed a formal objection to the inclusion of digital rights management (DRM) in HTML5, arguing that a draft proposal from the World Wide Web Consortium (W3C) could stymie Web innovation and block access to content for people across the globe.

The W3C's HTML working group is creating a technical standard for HTML5, an upcoming revision to the computer language that creates webpages and otherwise displays content online. The working group has accepted a draft that includes discussion of Encrypted Media Extensions (EME), which will hard-wire the requirements of DRM vendors into the HTML standard.

"This proposal stands apart from all other aspects of HTML standardization: it defines a new 'black box' for the entertainment industry, fenced off from control by the browser and end-user," said EFF International Director Danny O'Brien. "While this plan might soothe Hollywood content providers who are scared of technological evolution, it could also create serious impediments to interoperability and access for all."

DRM standards look like normal technical standards but turn out to have quite different qualities. They fail to implement their stated intention – protecting media – while dragging in legal mandates that chill the speech of technologists, lock down technology, and violate property rights by seizing control of personal computers from their owners. Accepting EME could lead to other rightsholders demanding the same privileges as Hollywood, leading to a Web where images and pages cannot be saved or searched, ads cannot be blocked, and innovative new browsers cannot compete without explicit permission from big content companies.

EFF filed this objection as its first act as a full member of W3C. EFF's goal is to broaden the discussion of the consequences of accepting DRM-based proposals like EME for the future of the Web.

"The W3C needs to develop a policy regarding DRM and similar proposals, or risk having its own work and the future of the Web become buried in the demands of businesses that would rather it never existed in the first place," said EFF Senior Staff Technologist Seth Schoen. "The EME proposal needs to be seen for what it is: a creation that will shut out open source developers and competition, throw away interoperability, and lock in legacy business models. This is the opposite of the fair use model that gave birth to the Web."]]></description>
<dc:subject>eff drm html html5 webstandards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:dd69703cf2a8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:eff"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webstandards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/josephschmitt/Clamp.js">
    <title>josephschmitt/Clamp.js · GitHub</title>
    <dc:date>2013-05-08T02:57:31+00:00</dc:date>
    <link>https://github.com/josephschmitt/Clamp.js</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Clamps an HTML element by adding ellipsis to it if the content inside is too long.]]></description>
<dc:subject>html webdesign webdevelopment plugin jquery javascript typography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:0b646a6d69f9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:plugin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:jquery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:typography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://37signals.com/svn/posts/3511-recent-versions-of-google-chrome-on-os-x">
    <title>Photo: Recent versions of Google Chrome on OS X… by Jason Z. of 37signals</title>
    <dc:date>2013-04-25T22:52:33+00:00</dc:date>
    <link>https://37signals.com/svn/posts/3511-recent-versions-of-google-chrome-on-os-x</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Recent versions of Google Chrome on OS X mangle native input buttons. I don’t know precisely when it started but no amount of CSS brute-force seems to correct the text alignment. Have you found a work-around? Do you know a little birdie on the Chrome team?]]></description>
<dc:subject>GoogleChrome osx webdevelopment webdesign css html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ce47e70c746b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:GoogleChrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://davidwalsh.name/download-attribute">
    <title>HTML5 download Attribute</title>
    <dc:date>2013-04-24T02:44:18+00:00</dc:date>
    <link>http://davidwalsh.name/download-attribute</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[I tend to get caught up on the JavaScript side of the HTML5 revolution, and can you blame me?  HTML5 gaves us awesome "big" stuff like WebSockets, Web Workers, History, Storage and little helpers like the Element classList collection.  There are, however, smaller features in HTML5 that we can appreciate; one of those would be the new download attribute.  The download attribute allows you to set a separate file download name than the actual link endpoint itself.]]></description>
<dc:subject>html html5 webdevelopment programming software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:c809200ee641/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/magic-numbers-in-css/">
    <title>Magic Numbers in CSS | CSS-Tricks</title>
    <dc:date>2013-04-23T00:09:49+00:00</dc:date>
    <link>http://css-tricks.com/magic-numbers-in-css/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Despite the super fun sounding name, magic numbers are a bad thing. It is an old school programming term for "unnamed numerical constant". As in, just some number plunked into the code that is probably vital to things working correctly but are very difficult for anyone not intimately familiar with the code to understand what it is for. CSS is loaded with unnamed numerical constants, but they are usually paired with properties and in the context of a selector so there is little mystery. There are magic numbers in CSS though, and they are still bad.


Magic numbers in CSS refer to values which "work" under some circumstances but are frail and prone to break when those circumstances change. They are usually always related to fonts in some way or another. They are created by an author who likely only tested in their own browser under ideal conditions. Let's take a look at some examples so we all know what they are and hopefully can avoid them in the future.]]></description>
<dc:subject>css webdesign webdevelopment programming software html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:67cb428bb2fb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tjvantoll.com/2013/04/15/list-of-pseudo-elements-to-style-form-controls/">
    <title>List of Pseudo-Elements to Style Form Controls - TJ VanToll - Tutorials, Thoughts, and Ramblings on Front End Development</title>
    <dc:date>2013-04-17T04:04:03+00:00</dc:date>
    <link>http://tjvantoll.com/2013/04/15/list-of-pseudo-elements-to-style-form-controls/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Styling form elements is a pain point when developing web applications. Historically, web developers have had to accept the form controls the browser provided with little hope of customization. However, web rendering engines are increasingly adding hooks through pseudo-elements to give authors some control over the display.

While all of these pseudo-elements are rendering engine specific (and therefore behind vendor prefixes), they can still be handy for customizing the display for that engine. The following is my best attempt at compiling a complete list of the pseudo-elements available in Trident, Gecko, and WebKit. At the time of this writing Blink is a recent fork of WebKit, so the pseudo-elements provided are identical. I am not aware of any form related pseudo-elements that Presto provides.]]></description>
<dc:subject>css css3 form html webdesign webdevelopment programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:c6ae3e4e0daf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:form"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://techblog.netflix.com/2013/04/html5-video-at-netflix.html">
    <title>The Netflix Tech Blog: HTML5 Video at Netflix</title>
    <dc:date>2013-04-16T06:56:29+00:00</dc:date>
    <link>http://techblog.netflix.com/2013/04/html5-video-at-netflix.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[We've been working with Google to implement support for the HTML5 Premium Video Extensions in the Chrome browser, and we've just started using this technology on the Samsung ARM-Based Chromebook. Our player on this Chromebook device uses the Media Source Extensions and Encrypted Media Extensions to adaptively stream protected content.  WebCrypto hasn't been implemented in Chrome yet, so we're using a Netflix-developed PPAPI (Pepper Plugin API) plugin which provides these cryptographic operations for now.  We will remove this last remaining browser plugin as soon as WebCrypto is available directly in the Chrome browser.  At that point, we can begin testing our new HTML5 video player on Windows and OS X.

 We're excited about the future of premium video playback on the web, and we look forward to the day that these Premium Video Extensions are implemented in all browsers!]]></description>
<dc:subject>netflix html5 html drm video software googlechrome internet browser standards w3c</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e6d38f72acf4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:googlechrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.guardian.co.uk/technology/blog/2013/mar/12/tim-berners-lee-drm-cory-doctorow?CMP=twt_fd">
    <title>What I wish Tim Berners-Lee understood about DRM | Technology | guardian.co.uk</title>
    <dc:date>2013-03-13T01:36:33+00:00</dc:date>
    <link>http://www.guardian.co.uk/technology/blog/2013/mar/12/tim-berners-lee-drm-cory-doctorow?CMP=twt_fd</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[This is the regime that the W3C stands to add to the Web, and that Berners-Lee has endorsed with his remarks. A regime where every improvement is seen as an opportunity to erect a toll booth. A Web built on the urinary tract infection business model: rather than getting your innovation in a healthy gush, every new feature must come in a painfully squeezed dribble, a few pennies if you want to link in directly to a specific timecode on the video; a few pennies more if you want to embed a link from the video to a web page, more if you want to move a video to another device or timeshift it, and so on.

As the leading standards-setting body for the Web, the W3C has an enormous, sacred and significant trust. The future of the Web is the future of the world, because everything we do today involves the net and everything we'll do tomorrow will require it. Now it proposes to sell out that trust, on the grounds that Big Content will lock up its "content" in Flash if it doesn't get a veto over Web-innovation. That threat is a familiar one: the big studios promised to boycott US digital TV unless it got mandatory DRM. The US courts denied them this boon, and yet, digital TV continues (if only Ofcom and the BBC had heeded this example before they sold Britain out to the US studios on our own high-def digital TV standards).

Flash is already an also-ran. As Berners-Lee himself will tell you, the presence of open platforms where innovation requires no permission is the best way to entice the world to your door. The open Web creates and supplies so much value that everyone has come to it – leaving behind the controlled, Flash-like environs of AOL and other failed systems. The big studios need the Web more than the Web needs big studios.

The W3C has a duty to send the DRM-peddlers packing, just as the US courts did in the case of digital TV. There is no market for DRM, no public purpose served by granting a veto to unaccountable, shortsighted media giants who dream of a world where your mouse rings a cash-register with every click and disruption is something that happens to other people, not them.]]></description>
<dc:subject>drm html html5 internet legal copyright technology hardware software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:2f2f9c6c7666/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://paulirish.com/2013/webkit-for-developers/">
    <title>WebKit for Developers - Paul Irish</title>
    <dc:date>2013-03-05T02:07:46+00:00</dc:date>
    <link>http://paulirish.com/2013/webkit-for-developers/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[First, let’s review the commonalities shared by all WebKit ports.

You know it’s funny. I tried writing this a few times. 
Each time I got corrected by Chrome team members, as you’ll see…
So first, WebKit parses HTML the same way. Well, except Chromium is the only port so far to enable threaded HTML parsing support.
… Okay, but once parsed, the DOM tree is constructed the same. Well, actually Shadow DOM is only turned on for the Chromium port, so DOM construction varies. Same goes for custom elements.
… Okay, well WebKit creates a window object and document object for everyone. True, though the properties and constructors it exposes can be conditional on the feature flags enabled.
… CSS parsing is the same, though. Slurping up your CSS and turning it into CSSOM’s pretty standard. Yeah, though Chrome accepts just the -webkit- prefix whereas Apple and other ports accept legacy prefixes like -khtml- and -apple-.
… Layout.. positioning? Those are the bread and butter. Same, right? Come on! Sub-pixel layout and saturated layout arithmetic is part of WebKit but differs from port to port.
Super.]]></description>
<dc:subject>webkit browser programming software standards css html safari googlechrome opera webdevelopment webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:73d72b93b7e9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webkit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:safari"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:googlechrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:opera"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/mixing-responsive-design-and-mobile-templates/">
    <title>Mixing Responsive Design and Mobile Templates | CSS-Tricks</title>
    <dc:date>2013-03-05T00:28:31+00:00</dc:date>
    <link>http://css-tricks.com/mixing-responsive-design-and-mobile-templates/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[You need a mobile strategy for your site. You have to pick Responsive Design or a dedicated mobile site, right? Maybe not. Maybe you can mix and match a variety of strategies.]]></description>
<dc:subject>webdesign webdevelopment software css html programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:1a648b0086e5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.netmagazine.com/opinions/jeffrey-zeldman-dream-standards-based-web">
    <title>Jeffrey Zeldman on the dream of a standards-based web | Opinion | .net magazine</title>
    <dc:date>2013-03-05T00:23:54+00:00</dc:date>
    <link>http://www.netmagazine.com/opinions/jeffrey-zeldman-dream-standards-based-web</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[By my lights, it succeeded around 2003, or maybe 2005. I was surprised that The Web Standards Project kept going as long as it did. From the outside, it sometimes seemed that nothing much was happening at The WaSP. But then again, this coincided with the period where IE6 stayed on the market for five or six years with no real changes, so it may have seemed like standards had been taken as far as they could be. From the outside, the persistence of webstandards.org was like the persistence of Dixieland music — a pleasant but fairly irrelevant reminder of the past!

Toward the end, over the past few years, I know there was some good educational work going on inside WaSP, although it wasn't always wildly apparent to the outside world, and I think many people's attention had moved on to other problems, such as multi-device design, which of course ironically recapitulates the whole standards struggle. (And standards are the answer in multi-device design as well. It's just that the standards that fully address some of the concerns of multi-device design are still evolving, like the devices—again, a perfect echo of the standards struggle during the years of the browser wars and Flash.) Once that educational piece got handed off to the W3C (finally!), it made sense for The WaSP to close up shop. And now they have.

A tip of the blue beanie to each and every person who helped make the dream of a standards-based web come true.]]></description>
<dc:subject>webdevelopment webdesign standards programming software css html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ffc4a767cefa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/aFarkas/html5shiv">
    <title>aFarkas/html5shiv · GitHub</title>
    <dc:date>2013-02-11T17:10:55+00:00</dc:date>
    <link>https://github.com/aFarkas/html5shiv</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[This script is the defacto way to enable use of HTML5 sectioning elements in legacy Internet Explorer.]]></description>
<dc:subject>html5 html programming javascript ie browser webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:651e0855d511/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:ie"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://intridea.github.com/stately/">
    <title>Stately | The simple map font</title>
    <dc:date>2013-02-07T07:27:28+00:00</dc:date>
    <link>http://intridea.github.com/stately/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Stately is a symbol font that makes it easy to create a map of the United States using only HTML and CSS. Each state can be styled independently with CSS for making simple visualizations. And since it's a font, it scales bigger and smaller while staying sharp as a tack.]]></description>
<dc:subject>css font map html webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b9be14d6960b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:font"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:map"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sencha.com/blog/the-making-of-fastbook-an-html5-love-story/">
    <title>The Making of Fastbook: An HTML5 Love Story | Blog | Sencha</title>
    <dc:date>2012-12-19T03:38:20+00:00</dc:date>
    <link>http://www.sencha.com/blog/the-making-of-fastbook-an-html5-love-story/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[We had our suspicions about why Facebook's mobile application team had problems, because it matched a common pattern. At Sencha, we build frameworks and tools for application developers, so we have pretty deep experience with development teams taking on HTML5 app projects. When a team has problems with HTML5, it usually stems from the fact that they take a “website” development approach to building an app, and often don't use the right tools and architectures for application development. This is what we suspected about the Facebook HTML5 app. The way that app performed — slow loading, choppy user experience in the News Feed, low framerate — exhibited the usual symptoms.

In any event, we knew HTML5 was, in fact, ready, and we wanted to prove it. So we took it upon ourselves to rebuild the challenging parts of the Facebook mobile application in HTML5 in our spare time. Today, we'd like to introduce you to Sencha Fastbook, a technology proof of concept that shows how fast HTML5 can be, and demonstrates how readily HTML5 can be used to handle the toughest app challenges.

This four-minute video gives you a quick overview of Sencha Fastbook, and shows you a side-by-side comparison of how well our HTML5 app performs against both the native iOS and the native Android Facebook apps (versions 5.2 and 1.9.12 respectively, the latest available when we made this video on December 10th). The rest of this post gets into the technical details of how we built Fastbook.]]></description>
<dc:subject>html5 html programming software softwareengineering mobile webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b2de9ac421f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://incident57.com/codekit/kit.php">
    <title>CodeKit — The Kit Language</title>
    <dc:date>2012-12-19T02:34:48+00:00</dc:date>
    <link>http://incident57.com/codekit/kit.php</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A .kit file is HTML with special comments.
Kit adds two things to HTML: imports and variables.
CodeKit compiles .kit files into regular HTML files.]]></description>
<dc:subject>html programming webdesign webdevelopment software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:aad48a9e179e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.campaignmonitor.com/blog/post/3890/adding-audio-to-email-newsletters">
    <title>Audio in email newsletters - are there really sound uses for it? - Campaign Monitor</title>
    <dc:date>2012-12-19T02:32:52+00:00</dc:date>
    <link>http://www.campaignmonitor.com/blog/post/3890/adding-audio-to-email-newsletters</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Well, you'll be pleased to know that you can play (and autoplay) music in HTML email, using the HTML5 <audio> tag. While this technique is only fully supported in Apple and iOS Mail (mind you, that's almost 50% of recorded opens), the faily-reliable display of fallback content in other clients makes it a possible addition to any email campaign.]]></description>
<dc:subject>audio html email webdesign html5</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:950a294fbd3a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:audio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/News/2012">
    <title>W3C News Archive: 2012 W3C</title>
    <dc:date>2012-12-18T15:41:41+00:00</dc:date>
    <link>http://www.w3.org/News/2012</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[W3C published today the complete definition of the HTML5 and Canvas 2D specifications. Though not yet W3C standards, these specifications are now feature complete, meaning businesses and developers have a stable target for implementation and planning. "As of today, businesses know what they can rely on for HTML5 in the coming years, and what their customers will demand," said Jeff Jaffe, W3C CEO. HTML5 is the cornerstone of the Open Web Platform, a full programming environment for cross-platform applications with access to device capabilities; video and animations; graphics; style, typography, and other tools for digital publishing; extensive network capabilities; and more. Read the full press release and W3C Member testimonials.
To reduce browser fragmentation and extend implementations to the full range of tools that consume and produce HTML, W3C now embarks on the stage of W3C standardization devoted to interoperability and testing. W3C is on schedule to finalize the HTML5 standard in 2014. In parallel, the W3C community will continue its work on next generation HTML features, including extensions to complement built-in HTML5 accessibility, responsive images, and adaptive streaming.
The HTML Working Group also published first drafts of HTML 5.1, HTML Canvas 2D Context, Level 2, and main element, providing an early view of the next round of standardization. Learn more About HTML.]]></description>
<dc:subject>w3c webdevelopment programming software standards html html5</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:f56208686556/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/docverter/docverter">
    <title>Docverter/docverter</title>
    <dc:date>2012-11-26T06:52:09+00:00</dc:date>
    <link>https://github.com/docverter/docverter</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Docverter is a document conversion server with an HTTP interface. It wrap the following open source software in a JRuby app:

Pandoc for plain text to HTML and ePub conversion
Flying Saucer for HTML to PDF
Calibre for ePub to MOBI conversion]]></description>
<dc:subject>conversion books document html epub pdf mobi http</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:12587bfcc800/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:conversion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:document"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:epub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:http"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://maker.github.com/ratchet/">
    <title>Ratchet</title>
    <dc:date>2012-11-15T10:26:28+00:00</dc:date>
    <link>http://maker.github.com/ratchet/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Prototype iPhone apps with simple HTML, CSS and JS components.]]></description>
<dc:subject>iphone prototype mobile ios programming software html css javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:d71236ad5fe4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:iphone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:prototype"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/the-facebook-loading-animation-in-css/">
    <title>The Facebook Loading Animation in CSS | CSS-Tricks</title>
    <dc:date>2012-11-06T23:55:52+00:00</dc:date>
    <link>http://css-tricks.com/the-facebook-loading-animation-in-css/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Hey everyone! CSS3 is just plain awesome. The development is fast and the possibilities are endless. Today I want to show you how to make an awesome animation using multiple background images and linear gradients in CSS. We will build the Facebook loading animation using just a single HTML element.

For simplicity, you will not see any vendor prefixes in the CSS. Before we dive into creating the Facebook loading animation I will explain the basic techniques.]]></description>
<dc:subject>html css css3 webdesign webdevelopment programming politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e1acbb542016/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.javierusobiaga.com/stop-using-the-viewport-tag-until-you-know-ho">
    <title>Stop using the viewport meta tag (until you know how to use it) - htmlboy</title>
    <dc:date>2012-10-29T03:23:43+00:00</dc:date>
    <link>http://blog.javierusobiaga.com/stop-using-the-viewport-tag-until-you-know-ho</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[If you are not coding a responsive site, just don't use any meta viewport. If you are coding a responsive website, all you need to write is

<meta name="viewport" 
content="width=device-width, initial-scale=1">
Any additional parameters in the content attribute usually screw up user's experience.

EDIT: As Brad Frost correctly pointed out, you should also use the viewport meta if you are building a dedicated mobile site, so it's not just for responsive sites.]]></description>
<dc:subject>html html5 webdesign webdevelopment programming MetaTag politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:5ee25a298e5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:MetaTag"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.brucelawson.co.uk/2012/on-drm-in-html5/">
    <title>Bruce Lawson’s personal site  : On DRM in HTML5</title>
    <dc:date>2012-10-29T02:59:32+00:00</dc:date>
    <link>http://www.brucelawson.co.uk/2012/on-drm-in-html5/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[I don’t want DRM. I dislike DRM. Not particularly because I think everything should be free (I don’t; I like receiving royalties for the best HTML5 book) but because I don’t think it works. The DRM graveyard: A brief history of digital rights management in music demonstrates this excellently.

However, “the suits” believe it does work, and aren’t willing to invest fully in the web stack until there is some attempt at DRM. That’s why Netflix, Google and Microsoft have proposed the Encrypted Media Extensions specification that’s being worked on by the Encrypted Media Task Force of the HTML Working Group at the W3C.]]></description>
<dc:subject>drm html html5 webdevelopment programming standards politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:f43fe9f91d96/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.webmonkey.com/2012/10/mozilla-plans-h-264-video-for-desktop-firefox/">
    <title>Mozilla Plans H.264 Video for Desktop Firefox - Wired.com</title>
    <dc:date>2012-10-24T05:42:36+00:00</dc:date>
    <link>http://www.webmonkey.com/2012/10/mozilla-plans-h-264-video-for-desktop-firefox/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The company’s recently released Firefox for Android already bakes in OS-level support for the H.264 video codec and now Mozilla is adding support to desktop Firefox as well.

Mozilla long opposed supporting the H.264 codec because it’s patent-encumbered and requires licensing fees. It’s also the most popular codec for HTML5 video on the web, which drove Mozilla to swallow its ideals and get practical about adding support to Firefox. Instead of including the codec directly in Firefox, the browser will rely on OS-level tools to play H.264 video.

There’s still no support for H.264 in the current desktop version of Firefox, but as Mozilla CTO, Brendan Eich recently noted on his blog, work is under way and, with the exception of Windows XP, all platforms will get OS-native codec support for H.264 video. Windows XP, which lacks OS-level tools for H.264, will continue to use the Flash plugin to play H.264 movies.

If you’d like to keep track of Mozilla’s progress adding H.264 to the desktop there’s a tracking bug that follows solutions for all the major desktop platforms. Eich does not give an explicit timeline or any hint of when H.264 support might ship with Firefox on the desktop.

The HTML5 video element was supposed to offer a standards-based way to play movies on the web without proprietary plugins like Flash or Silverlight. Unfortunately that dream has failed to pan out. Instead of proprietary plugins, the web ended up with proprietary video codecs, which has created a split in browser support for HTML5 video. Firefox and Opera support the open Ogg and WebM codecs, while Safari and Internet Explorer supported H.264.

Mozilla (and Opera) were against the adoption of H.264 on ideological grounds — H.264 is not an open codec and requires that companies using it pay royalties. But earlier this year the company partially reversed course and said it would support H.264 on devices where the codec is supplied by the platform or implemented in hardware.

]]></description>
<dc:subject>MozillaFirefox h.264 codec video browser Internet standard html5 HTML politics</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:8e0d1525d4cd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:MozillaFirefox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:h.264"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:codec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:Internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:HTML"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stopdesign.com/archive/2012/10/11/ten-years-later.html">
    <title>Ten years later</title>
    <dc:date>2012-10-12T02:58:33+00:00</dc:date>
    <link>http://stopdesign.com/archive/2012/10/11/ten-years-later.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Ten years ago today, we pulled back the curtains on a redesign of Wired.com. The actual design and the code that rendered it is long gone. But they were significant in their time.

The redesign of Wired News in 2002 marked the first time a large, well-known, daily-content publisher had dropped tables for layout, and embraced the separation of markup and style in a rather new (at the time) approach to web design. Several prominent blogs, and niche content sites (zeldman.com, meyerweb.com, alistapart.com) had broken ground, and were already using and evangelizing a greater adoption of Web Standards.

Halfway through the redesign process, I started plotting how Wired could support the standards movement not just by publishing stories about it, but by adopting it outright. If pure, valid XHTML to mark up the content and simple CSS for layout and style was enough for other sites, it should work for Wired too. I contacted Jeffrey Zeldman and Eric Meyer to let them know what we were up to. Their excitement over the prospect of Wired jumping on board hinted that this might be a big deal. We dove in head first, and never looked back. Not long after Wired took that leap, many other large, well-known sites and companies began following suit.]]></description>
<dc:subject>webdesign css html politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:f41eea7efc25/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://codepen.io/joshnh/pen/ohbHl">
    <title>Pure CSS Under Construction GIF · CodePen</title>
    <dc:date>2012-10-03T15:35:30+00:00</dc:date>
    <link>http://codepen.io/joshnh/pen/ohbHl</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[1) @paul_irish #lazyweb's wanting classic  construction man GIF in CSS

2) @_joshnh builds on @CodePen with 1 element ]]></description>
<dc:subject>gif css css3 html webdesign politics</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:fff102d26aa9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:gif"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.campaignmonitor.com/blog/post/3780/removing-the-60-character-line-limit-on-plain-text-email">
    <title>Removing the 60 character line limit on plain-text email - Campaign Monitor</title>
    <dc:date>2012-08-23T05:56:04+00:00</dc:date>
    <link>http://www.campaignmonitor.com/blog/post/3780/removing-the-60-character-line-limit-on-plain-text-email</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Our new recommendation is simple - when designing plain text emails, let text wrap naturally, instead of manually inserting line breaks into paragraphs.]]></description>
<dc:subject>email design css html politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:421f29e7a001/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nczonline.net/blog/2012/08/22/the-innovations-of-internet-explorer/">
    <title>The innovations of Internet Explorer</title>
    <dc:date>2012-08-23T00:00:42+00:00</dc:date>
    <link>http://www.nczonline.net/blog/2012/08/22/the-innovations-of-internet-explorer/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[While it’s easy and popular to poke at Internet Explorer, in reality, we wouldn’t have the web as we know it today if not for its contributions. Where would the web be without XMLHttpRequest and innerHTML? Those were the very catalysts for the Ajax revolution of web applications, upon which a lot of the new capabilities have been built. It seems funny to look back at the browser that has become a “bad guy” of the Internet and see that we wouldn’t be where we are today without it.

Yes, Internet Explorer had its flaws, but for most of the history of the Internet it was the browser that was pushing technology forward. Now that were in a period with massive browser competition and innovation, it’s easy to forget where we all came from. So the next time you run into people who work on Internet Explorer, instead of hurling insults and tomatoes, say thanks for helping to make the Internet what it is today and for making web developers one of the most important jobs in the world.]]></description>
<dc:subject>internet ie webdesign webdevelopment programming dom ajax javascript html politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:14f7dd85db79/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:ie"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:dom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.campaignmonitor.com/blog/post/3795/outlook-2013-says-no-to-empty-table-cells">
    <title>Outlook 2013 doesn’t respect height in empty table cells</title>
    <dc:date>2012-08-21T05:08:52+00:00</dc:date>
    <link>http://www.campaignmonitor.com/blog/post/3795/outlook-2013-says-no-to-empty-table-cells</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[If you’re already testing your email newsletters in Outlook 2013 Preview, then you may have noticed a little more whitespace than expected.

While Outlook 2013 may have much in common with its predecessors, Outlook 2010 and 2007, the differences are starting to appear. In this case, empty table cells (or cells containing a & nbsp;) now have a minimum height of roughly 15px, regardless of what you’ve set a cell’s height attribute to be.

This can be particularly irritating if you’ve used empty table cells to create margins/padding between paragraphs of text and around images (for clients that do not support these CSS properties), or when creating ‘bulletproof’ horizontal rules. However, there is a rather strange solution. For example, say you have an empty cell with height="1" like this:

<td height="1" bgcolor="#cccccc"></td>
Unfortunately, Outlook 2013 will give this cell a height of 15px or so by default, unless you add… You guessed it, style="font-size: 1px;" (where 1px is the cell height you’re after).

Yes, adding a font size to your inline CSS styles fixes this bug. Here’s the updated code:

<td height="1" bgcolor="#cccccc" style="font-size: 1px;"></td>
Unfortunately, you’ll need to add this inline style to all empty cells individually, as elegant CSS workarounds like td[height="1"] { font-size: 1px; } are not supported in Outlook 2013 Preview.]]></description>
<dc:subject>outlook html email design webdesign politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:f894955f3f15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:outlook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/arturadib/strapdown">
    <title>arturadib/strapdown</title>
    <dc:date>2012-08-15T03:21:16+00:00</dc:date>
    <link>https://github.com/arturadib/strapdown</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Strapdown.js makes it embarrassingly simple to create elegant Markdown documents. No server-side compilation required.]]></description>
<dc:subject>markdown html javascript programming webdevelopment politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:0cff512b21e8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://humblesoftware.com/flotr2/">
    <title>Flotr2 : a library for drawing HTML5 charts and graphs (humblesoftware.com)</title>
    <dc:date>2012-05-17T00:31:50+00:00</dc:date>
    <link>http://humblesoftware.com/flotr2/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[RT @hackernewsbot: Flotr2 : a library for drawing HTML5 charts and graphs... ]]></description>
<dc:subject>HTML html5 graphing politics</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:131676355f7e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:HTML"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:graphing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/saving-the-day-with-scoped-css/">
    <title>Saving the Day with Scoped CSS</title>
    <dc:date>2012-04-19T02:33:04+00:00</dc:date>
    <link>http://css-tricks.com/saving-the-day-with-scoped-css/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Over the last couple years HTML5 and CSS3 have rocked our worlds and the way we approach common website issues. Every few days it seems there is some new fangled snippet or approach that is a game changer. Today might just be another one of those days (kind of).

One little known feature of HTML5 is Scoped CSS. It’s an attribute for style blocks that may change the way we tackle certain styling challenges in the future.]]></description>
<dc:subject>html5 css3 css html webdesign webdevelopment programming politics</dc:subject>
<dc:identifier>https://pinboard.in/u:jtyost2/b:05f4ab658c29/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ryancollins.me/?p=1041">
    <title>Pure CSS Clickable Events Without :target</title>
    <dc:date>2012-03-22T06:55:44+00:00</dc:date>
    <link>http://www.ryancollins.me/?p=1041</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Click on the drop downs above. That’s done all in CSS; no kind of javascript whatsoever. Pretty cool, eh? It’s a fun use of the :active and :hover selectors. You can browse the source code for the demo above here. If you’d like a more in-depth tutorial of how to accomplish this, continue reading.]]></description>
<dc:subject>css dropdown menu clickevent html programming webdesign webdevelopment politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:75d8e4ddc0df/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:dropdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:menu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:clickevent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://designshack.net/articles/css/whats-the-deal-with-display-inline-block/">
    <title>What’s the Deal With Display: Inline-Block? | Design Shack</title>
    <dc:date>2012-03-18T19:14:02+00:00</dc:date>
    <link>http://designshack.net/articles/css/whats-the-deal-with-display-inline-block/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[To be honest, I’ve never really played around with inline-block too much before today, but I’ve been seeing more and more suggestions in the comments that I explore this method as an alternative to floats so I thought I’d take the advice. I was hopeful going into it that it was indeed some magic, no-hassle way around floats, but in truth it really isn’t. There are still several unexpected behaviors that you have to know about and respond to, resulting in some hacky code much like we often see with float clearing fixes.

To be fair though, it is in fact a pretty simple way to accomplish float-like layouts. More importantly, the CSS that you have to implement to make sure it’s cross-browser compatible is briefer than even the popular micro clearfix hack from Nicolas Gallagher. This may make it a better way to go for many projects.

Ultimately, I think I will in fact begin adding this method to my bag of tricks. I suspect that certain times will arise when floats aren’t ideal (example: right floats render everything in reverse) and this will be a great alternative to have in those situations.

What do you think? Is inline-block a good alternative to floats? What situations can you think of where one clearly has an advantage over the other?]]></description>
<dc:subject>programming CSS HTML webdesign politics</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:9f20501e6e03/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:CSS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:HTML"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/darcyclarke/Front-end-Developer-Interview-Questions">
    <title>darcyclarke/Front-end-Developer-Interview-Questions</title>
    <dc:date>2012-03-08T07:24:46+00:00</dc:date>
    <link>https://github.com/darcyclarke/Front-end-Developer-Interview-Questions</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A list of questions you can use to help interview potential candidates for a front-end development position.]]></description>
<dc:subject>programming css html javascript interview career work politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:8e2d371e3166/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:interview"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.frankieroberto.com/responsive_text">
    <title>Responsive text</title>
    <dc:date>2012-02-16T06:32:45+00:00</dc:date>
    <link>http://www.frankieroberto.com/responsive_text</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Some websites now contain 'responsive images'. These scale (or crop) depending upon your screen's viewing area, so the image sizes remain appropriate whether you're looking at the website on a mobile phone, or on a huge flat screen monitor.

This is an example of responsive text.

The amount of textual detail scales relative to your screen size.

The effect is achieved using simple HTML class names and CSS media queries which show or hide the content depending upon the current screen width.]]></description>
<dc:subject>webdesign webdevelopment programming software html css css3 design politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:1a27ffdecc80/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#the-translate-attribute">
    <title>3.2 Elements — HTML Standard</title>
    <dc:date>2012-02-08T03:18:39+00:00</dc:date>
    <link>http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#the-translate-attribute</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The translate attribute is an enumerated attribute that is used to specify whether an element's attribute values and the values of its Text node children are to be translated when the page is localized, or whether to leave them unchanged.

The attribute's keywords are the empty string, yes, and no. The empty string and the yes keyword map to the yes state. The no keyword maps to the no state. In addition, there is a third state, the inherit state, which is the missing value default (and the invalid value default).]]></description>
<dc:subject>html standards webdesign webdevelopment programming politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:2cb5df8f17b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dev.w3.org/csswg/css3-hierarchies/">
    <title>CSS Hierarchies Module Level 3</title>
    <dc:date>2012-02-07T05:03:57+00:00</dc:date>
    <link>http://dev.w3.org/csswg/css3-hierarchies/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This module contains the features of CSS level 3 relating to the hierarchical nesting of style rules. It includes and extends the functionality of CSS level 2 [CSS21], which builds on CSS level 1 [CSS1]. The main extension compared to level 2 is the ability to nest a style rule within another rule, allowing greater modularisation and readibility of CSS documents.]]></description>
<dc:subject>css html css3 w3c standards webdesign webdevelopment programming politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:463184e0b031/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://davidwalsh.name/prevent-form-autocomplete">
    <title>Prevent Form Field Autocomplete</title>
    <dc:date>2012-02-04T22:23:35+00:00</dc:date>
    <link>http://davidwalsh.name/prevent-form-autocomplete</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Preventing autocompletion of form fields is incredibly important since we never know where our users are completing them from. They could complete them from a super secure computer or an incredibly public computer. Regardless of security level, some field values should never be remembered, like credit card number, social security number, etc. Preventing autocompletion is as simple as adding one attribute to a FORM tag for individual form fields.]]></description>
<dc:subject>html5 html security programming webdevelopment politics</dc:subject>
<dc:identifier>https://pinboard.in/u:jtyost2/b:925280fb9d77/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/034506.html">
    <title>[whatwg] Requests for new elements for comments</title>
    <dc:date>2012-01-26T07:18:25+00:00</dc:date>
    <link>http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/034506.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[We already have an element for comments and other self-contained document 
modules, namely, <article>. The spec in fact specifically calls out an 
<article> nested in another <article> as being, by definition, a comment 
on the outer <article>.]]></description>
<dc:subject>html html5 programming webdesign webdevelopment WHATWG w3c politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ef1a9b5babb8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:WHATWG"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/mathiasbynens/jquery-placeholder">
    <title>mathiasbynens/jquery-placeholder - GitHub</title>
    <dc:date>2011-12-30T17:53:23+00:00</dc:date>
    <link>https://github.com/mathiasbynens/jquery-placeholder</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A jQuery plugin which enables HTML5 placeholder behavior for browsers that aren’t trying hard enough yet]]></description>
<dc:subject>jquery html html5 placeholder webdevelopment webdesign programming form politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:5f29e5042a12/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:jquery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:placeholder"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:form"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://html5doctor.com/the-output-element/">
    <title>The output element | HTML5 Doctor</title>
    <dc:date>2011-12-30T17:33:43+00:00</dc:date>
    <link>http://html5doctor.com/the-output-element/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Across the web, you’ll see a range of sites that feature calculators for working out things like loan repayments, mortgage rates, tax, insurance, and more. Until now, we’ve had no way of semantically marking up the result of those calculations. Enter: the <output> element! In this article, we’ll show you <output> and some related JavaScript tricks. Let’s get cracking.]]></description>
<dc:subject>html html5 webdesign webdevelopment programming javascript politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b081541964e6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Browser-Polyfills">
    <title>HTML5 Cross Browser Polyfills - GitHub</title>
    <dc:date>2011-12-14T17:38:16+00:00</dc:date>
    <link>https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Browser-Polyfills</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[So here we're collecting all the shims, fallbacks, and polyfills in order to implant html5 functionality in browsers that don't natively support them.

The general idea is that: we, as developers, should be able to develop with the HTML5 apis, and scripts can create the methods and objects that should exist. Developing in this future-proof way means as users upgrade, your code doesn't have to change but users will move to the better, native experience cleanly.

Looking for a way to conditionally load these scripts client-side based on feature detects? See Modernizr. Looking for a guide to writing your own polyfills? See Writing Cross-Browser JavaScript Polyfills.]]></description>
<dc:subject>html5 css3 css html programming polyfill shim javascript webdevelopment politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:57ffa7cb0582/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:polyfill"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:shim"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/necolas/css3-social-signin-buttons">
    <title>necolas/css3-social-signin-buttons - GitHub</title>
    <dc:date>2011-11-27T22:11:12+00:00</dc:date>
    <link>https://github.com/necolas/css3-social-signin-buttons</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[CSS3 Social Sign-in Buttons with icons. Small and large sizes.]]></description>
<dc:subject>css css3 webdesign webdevelopment buttons programming html politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:1bf7cc3c1411/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:buttons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/DataZombies/DBi">
    <title>DataZombies/DBi - GitHub</title>
    <dc:date>2011-11-25T23:12:31+00:00</dc:date>
    <link>https://github.com/DataZombies/DBi</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[DBi handles all the work of creating an iOS or Safari WebSQL database and manages local/session storages.

DBi creates, tables, indices, triggers & views and populates the tables all from a single JSON file that's outputted from DBi.]]></description>
<dc:subject>html5 localstorage websql html javascript programming webdevelopment webdesign politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:c846035ab910/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:localstorage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:websql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/TapQuo/Lungo.js">
    <title>TapQuo/Lungo.js - GitHub</title>
    <dc:date>2011-11-09T01:32:14+00:00</dc:date>
    <link>https://github.com/TapQuo/Lungo.js</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[LungoJS
HTML5 Mobile Framework, and stuff.]]></description>
<dc:subject>javascript html5 css3 css html framework mobile MobileFramework politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b2fedae8763c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:MobileFramework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/dnewcome/Donatello">
    <title>dnewcome/Donatello - GitHub</title>
    <dc:date>2011-10-11T23:53:49+00:00</dc:date>
    <link>https://github.com/dnewcome/Donatello</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Donatello is a pure-CSS drawing library for the browser. The API is inspired in part by Raphael.js. All graphical elements are rendered using HTML DOM and CSS. The idea came together from various code snippets I had lying around for drawing circles and lines in other projects. I decided to make an attepmpt at a drawing API using these ideas after using Raphael.js in my Node Knockout team project.]]></description>
<dc:subject>css javascript library raphael.js donatello html api politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:0f52561a1e3c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:raphael.js"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:donatello"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/zynga/scroller">
    <title>zynga/scroller - GitHub</title>
    <dc:date>2011-10-03T02:14:30+00:00</dc:date>
    <link>https://github.com/zynga/scroller</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Accelerated panning and zooming for HTML and Canvas]]></description>
<dc:subject>html5 html canvas javascript programming scrolling zooming politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e2e48bb0347f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:canvas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:scrolling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:zooming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://octopress.org/">
    <title>Octopress</title>
    <dc:date>2011-09-26T03:24:38+00:00</dc:date>
    <link>http://octopress.org/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Octopress is a framework designed by Brandon Mathis for Jekyll, the blog aware static site generator powering Github Pages. To start blogging with Jekyll, you have to write your own HTML templates, CSS, Javascripts and set up your configuration. But with Octopress All of that is already taken care of. Simply clone or fork Octopress, install dependencies and the theme, and you’re set.]]></description>
<dc:subject>Jekyll HTML CSS JavaScript framework blogging politics</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:8779a51df3f0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:Jekyll"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:HTML"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:CSS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:JavaScript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:blogging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://leaverou.me/2011/09/pure-css3-typing-animation-with-steps/">
    <title>Pure CSS3 typing animation with steps() | Lea Verou</title>
    <dc:date>2011-09-06T02:37:32+00:00</dc:date>
    <link>http://leaverou.me/2011/09/pure-css3-typing-animation-with-steps/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[steps() is a relatively new addition to the CSS3 animations module. Instead of interpolating the values smoothly, it allows us to define the number of “frames” precisely. So I used it to create headers that have the well-known animated “typing effect”:]]></description>
<dc:subject>css css3 html webdesign webdevelopment programming politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:aa6091b0aee1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arstechnica.com/open-source/news/2011/09/reflecting-on-chrome-as-browser-hits-third-birthday.ars">
    <title>Reflecting on Chrome as browser hits third birthday</title>
    <dc:date>2011-09-03T02:12:57+00:00</dc:date>
    <link>http://arstechnica.com/open-source/news/2011/09/reflecting-on-chrome-as-browser-hits-third-birthday.ars</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Google launched its Chrome Web browser on September 1, 2008—three years ago today. In the time since its debut, Google's Web browser has attracted a considerable following and influenced other browser vendors. To celebrate the anniversary, Google has published an interactive HTML5 infographic that presents the history of the major Web browsers and Web standards.

Chrome's contributions to the Web and browser design are significant. Google set the pace of development for modern browsers by being the first browser vendor to adopt a radically shorter development cycle and a release management strategy that emphasizes fast-paced incremental improvement. Chrome's transparent update system and channel-based prerelease distribution model are being adopted by Firefox and could eventually be picked up by other browser vendors.

Chrome's distinctive minimalist design has also changed the way that browser vendors think about usability. Chrome's approach to paring down the interface and offering a more streamlined user experience has been embraced by other browsers. Google took the lead on some controversial moves, like not displaying "http" in the location bar.

The technical influence of Chrome can even be felt outside of the browser ecosystem. The performance of Chrome's sophisticated V8 JavaScript engine and the ease with which it can be embedded in other software have led to its adoption in a range of other environments. For example, V8 was used to produce Node.js, a server-side JavaScript runtime that is popularizing the use of JavaScript for backend Web development.

Although Chrome has come a long way, the browser still lags behind its competitors in some key ways. When we first reviewed Chrome in 2008, one of our biggest gripes with the user interface was the lack of tab overflow handling. After three years, this issue still hasn't been fixed. Chrome's user interface for browsing history is another major weak area relative to other browsers. History autocompletion in the Omnibox is also quite limited compared to Firefox's AwesomeBar.

Despite the limitations, Chrome's audience has grown explosively since its 2008 launch. According to statistics from StatCounter, the browser's marketshare hit 10 percent last year and continued growing to 23 percent, as of this month. It's become an important part of Google's product landscape, serving as the central pillar of the company's ambitious Chrome OS operating system.

After three great years of innovation and raising the bar, Chrome's future looks bright.]]></description>
<dc:subject>googlechrome browser javascript html html5 css css3 webdesign webstandards webdevelopment politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:11527ccab29a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:googlechrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webstandards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/imakewebthings/deck.js">
    <title>imakewebthings/deck.js - GitHub</title>
    <dc:date>2011-08-24T08:05:49+00:00</dc:date>
    <link>https://github.com/imakewebthings/deck.js</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A JavaScript library for building modern HTML presentations. deck.js is flexible enough to let advanced CSS and JavaScript authors craft highly customized decks, but also provides templates and themes for the HTML novice to build a standard slideshow.]]></description>
<dc:subject>html programming html5 javascript jquery css presentation politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:3dc23189180a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:jquery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:presentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>