Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs











More recommended blogs »

Here are posterous posts filed under html5...

HTML5 provides a new tool set for artistic developers. Cool apps cometh.

http://9elements.com/io/projects/html5/canvas/

Filed under: html5

- VoteLinks

“Indexing and tracking applications treat all links as endorsements, or expressions of support. This is a problem, as we need to link to those we disagree with as well, to discuss why.”

By including the attributes: rev=”vote-for” or rev=”vote-against” we can indicate in the hyperlink whether we agree with the sentiment in the linked to post, or not. Cool.

Looking ahead, search engines will be able to have more insight into what type of relationships a website has with another via HTML5's VoteLink attribute, as well as the existing "nofollow" for commerical links.

Search results could start showing the equivalent of antonyms on viewpoints - a search for "Labour" could display the most vilified Conservative result as well. (quite difficult in today's centrist politics!)

Filed under: html5, search, VoteLinks

Did you catch that? I changed <h2> element to an <h1>. But…but…but… shouldn’t you only have one <h1> per document? Won’t this screw up the document outline? No, and here’s why. In HTML 4, the only way to create a document outline was with the <h1><h6> elements. If you only wanted one root node in your outline, you had to limit yourself to one <h1> in your markup. But the HTML5 specification defines an algorithm for generating a document outline that incorporates the new semantic elements in HTML5. The algorithm says that an <article> element creates a new section (i.e. a new node in the document outline). And in HTML5, each section can have its own <h1> element.

To be HTML5 compliant, a best practice SEO standard of only one H1 per page would be broken - more markup around sections such as <article> means each section can have its on H1-6 structure, <hgroup>, meaning multiple H1's

Filed under: h1, html5, seo

smarthive says...

USB 3.0 and 3d TV are sounding pretty nifty, much less AR (augmented reality) contact lenses? Wondering wear haptic tech and voice recognition come into play with all of this?

Filed under: 3d TV, AR, augmented reality, augmented reality contact lenses, future, HTML5, new tech, new technologies, PC World, smarthive, technology, USB 3.0

Spyros says...

Cool article by Smashing Magazine about CSS3 and HTML 5 layouts and how they will change things for Web Design in the future.

Filed under: CSS Layouts, CSS styles, CSS3, HTML, HTML5, Smashing Magazine

quaternion says...

Done any experiments with next generation browser technologies? I'm
building a library of articles and resources on HTML5:

* Offline Storage
* Geolocation APIs
* Javascript workers
* Canvas
* SVG
* ... and much more

Have a favorite article or tool on HTML5? I'd love to hear about it.

Filed under: html5, web, web development

Lrock says...

Filed under: Google, html5, Tutorial

veruus says...

Filed under: html5, theinternetisawesome

lukasztyrala says...

No browser is perfect as we can see, but some are definitely ahead. The
http://findmebyip.com/ is quite useful. It would be great to see it
detecting JavaScript, Flash and Java version also.

Filed under: browsers, chrome, css3, firefox, html5, ie, opera

pbprado says...

O Google anunciou nesta terça-feira o lançamento do seu Google Chrome Frame, plug-in que permitirá aos usuários do Internet Explorer (IE), da Microsoft, o acesso às tecnologias do navegador Chrome, como mais opções de aplicativos online e maiores velocidades de download.

O Google Chrome Frame permite que o IE use HTML5 e outras tecnologias de código aberto, o que inclui grandes melhoras de desempenho de JavaScript. Uma das maiores barreiras para a utilização em massa do HTML5 é a falta de suporte do IE para o padrão.

Quando os usuários instalam o plug-in e os desenvolvedores adicionam uma tag de compatibilidade X-UA, o navegador consegue renderizar páginas com elementos de HTML5 ¿ assim, os sites podem usar o padrão sem sacrificar grande parte de sua potencial base de visitantes. Sem a tag X-UA, as páginas são renderizadas pelo IE normalmente, usando o seu engine Trident em vez do engine do Chrome, baseado no WebKit.

Uma das maiores vantagens para o Google em disponibilizar o plug-in é assegurar a compatibilidade do IE com o Google Wave. O plug-in ainda oferece suporte a recursos offline do HTML5 e à tag canvas. Não é segredo que o Google acredita que o desktop tradicional está ficando para trás, e possibilitar e incentivar o uso de HTML5 e JavaScript de alto desempenho é mais um passo para emular um ambiente desktop na web.

O plug-in, por enquanto, está disponível para desenvolvedores e programados em um versão de teste, compatível com as versões 6, 7 e 8 do Internet Explorer, e disponível no site code.google.com/chrome/chromeframe.

Fonte: SEMBrasil

Filed under: chrome, chrome frame, google, guerra dos navegadores, html5, internet, internet explorer 8, javascript, nas nuvens, navegadores