{"authorId":1,"title":{"title":{}},"slug":"my-web-wish-list","postDate":1180320273,"expiryDate":null,"enabled":1,"fields":{"2":"<p>My birthday is coming up on Thursday, so I thought I would make up a list of 5 things I wish to happen with the web in the next year. I know that most of these will not happen in that time frame, but I can at least wish right?<\/p>\n<!--more-->\n<h2>The List<\/h2>\n\n<p>In no particular order, this is what I want:<\/p>\n\n<ol>\n <li>For everyone running IE6 to be upgraded by automatic updates<\/li>\n<li>For the term &ldquo;Web 2.0&rdquo; to never be heard again<\/li>\n<li>For all standards compliant browsers to support attaching multiple background images using CSS<\/li>\n<li>For the ability to render <strong>all<\/strong> fonts on the web<\/li>\n<li>For all standards compliant browsers to support the nth-child selector<\/li>\n<\/ol>\n\n<h3>For everyone running IE6 to be upgraded by automatic updates<\/h3>\n\n<p>As all web developers have experienced, <strong>IE6 sucks<\/strong>. But there is good news; IE7 is a huge step forward. Sure it still has some of the same problems that IE6 had, but it is basically on par with other standards compliant browsers.<\/p>\n\n<p>Thankfully, Microsoft is pushing out IE7 in their automatic updates, and the number of people upgrading is rising quickly. Before we know it, IE6 will no longer be the most popular browser any more.<\/p>\n\n<h3> For the term &ldquo;Web 2.0&rdquo; to never be heard again<\/h3>\n\n<p>I&rsquo;m sick of it. The term is used everywhere, even job descriptions. There was a good article on Fadtastic, <a href=\"http:\/\/fadtastic.net\/2007\/05\/17\/weekly-thought-why-good-designers-should-stop-saying-web-20\/\"> Weekly Thought: Why Good Designers Should Stop Saying &ldquo;Web 2.0&rdquo;<\/a>.<\/p>\n\n<p>&ldquo;Web 2.0&rdquo; is meaningless, and it needs to be vanished from everyone&rsquo;s vocabulary.<\/p>\n\n<h3>For all standards compliant browsers to support attaching multiple background images using CSS<\/h3>\n\n<p>Safari already does, why don&rsquo;t other standards compliant browsers? Just take a moment and think about how wonderfully simple the markup would be for rounded corners. Ahh maybe some day.<\/p>\n\n<h3> For the ability to render all fonts on the web<\/h3>\n\n<p>Why can&rsquo;t we upload fonts to our servers and have the browsers download them when needed? It can&rsquo;t be the technology. It seems like a simple task. Can you image the possibilities if designers were not restricted to web-safe fonts? While, <a href=\"http:\/\/www.mikeindustries.com\/sifr\/\">sIFR<\/a> is awesome, there are so many limits to it. This needs to happen, <strong>now<\/strong>.<\/p>\n\n<h3>For all standards compliant browsers to support the nth-child selector<\/h3>\n\n<p>No more JavaScript striping. No more using odd and even classes.<\/p>\n\n<p>When browsers support <a href=\"http:\/\/www.w3.org\/TR\/css3-selectors\/#structural-pseudos\">Structural Pseudo-Classes<\/a>, or more specifically, the n-th child selector, it&rsquo;s going to be great. We can handle all of the alternating styles that we want using only CSS.<\/p>\n\n<h4>What else?<\/h4>\n\n<p>So what are you getting me? What else would you ask for?<\/p>","4":{"website":{}}}}