It’s just data

Best Standards Support

Chris Wilson: If you (the page developer) really want the best standards support IE8 can give, you can get it by inserting a simple <meta> element. Aaron gives more details on this in his article.

Aaron Gustafson: This option, though strongly discouraged, will cause a site to target the latest IE browser versions as they release.

My basic problem is that I don’t know what features are in and out of IE8 or when it will be released.  I don’t even have access to a simple screenshot.

I simply want to code to standards, and hope that Microsoft will keep up as best of their ability.  Accordingly, I’ve implemented the following in my .htaccess file:

BrowserMatch MSIE best-standards-support
Header set X-UA-Compatible IE=edge env=best-standards-support

See also: loose coupling.

Update: Upon further reflection, I now have some questions:


...that also implies:

  Vary: User-Agent

right?

Posted by Julian Reschke at

They should ship that with Apache.

Posted by Anne van Kesteren at

Btw, if you want CSS rules to apply to unknown elements in IE, you just have to do document.createElement(elementName). This somehow lets the CSS engine know that elements with that name exist.

Posted by Sjoerd Visscher at

Julian Reschke: Since exactly the same content is sent from the server to the client, I do not see any need for a Vary HTTP header.

Posted by Alkarex at

Sam Ruby: Best Standards Support

wearehugh : Sam Ruby: Best Standards Support Tags : webstandards...

Excerpt from HotLinks - Level 1 at

Sam Ruby: Best Standards Support

[link]...

Excerpt from del.icio.us/wearehugh at

Vary: User-Agent

Hmmm.  Trading off cache efficiency for consistent rendering in IE.  Tough call.  For now, I’ll leave it as is as there are no released browsers that support this.  Eventually, I may have to send the header unconditionally.  I just hope that every browser vendor doesn’t feel entitled to create headers such as this.

document.createElement(elementName)

Thanks!  That does make a noticeable improvement.

Posted by Sam Ruby at

Julian Reschke: as a second thought, since there is indeed a BrowserMatch combined with the env parameter of Header, there should be a Vary: User-Agent in the HTTP headers. Otherwise, there is a risk that some Internet Explorer clients may receive from a cache a version without this X-UA-Compatible header (if it was first requested by a non-IE client).

But if one decide to use this feature, is it interesting to send this X-UA-Compatible only to IE clients? IMHO, there would be less harm in sending this header to any client, than to send it to IE only and reduce caching efficiency.

Posted by Alkarex at

This is ridiculous. This is the bobbing head bird with the glass of water. Yes, Microsoft. Indeed, Microsoft. Whatever you want, Microsoft.

If you want to code to standards, code to standards. Either IE does it right, without these little embellishments, or it doesn’t and people will eventually realize that IE is Bad.

I cannot believe how many people are following along on this one. We’re adding crap to our pages purely because Microsoft screwed up.

Boggles.

Posted by Shelley at

IE8 e Compatibilidade

Com o IE8 vindo por aí, com um renderizador completamente novo, é óbvio que uma das maiores preocupações dos desenvolvedores é o quanto essas mudanças vão ajudar–ou atrapalhar–a criação de novos sites e aplicativos e como fica a questão...

Excerpt from Superfície Reflexiva at

Bobbing Heads and the IE8 Meta Tag

I was astonished to read the A List Apart article Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8 and even more astonished to read compliance with the message from Eric Meyer, Molly Holzschlag, and the WaSP organization. How the mighty...

Excerpt from Bb's RealTech at

A quote from Sjoerd Visscher

If you want CSS rules to apply to unknown elements in IE, you just have to do document.createElement(elementName). This somehow lets the CSS engine know that elements with that name exist. - Sjoerd Visscher...

Excerpt from Simon Willison's Weblog at

IE8 Compatibility with X-UA-Compatible

If you want compatibility to work well in IE8 and lower, then it is time to get to know the X-UA-Compatible header. This is according to Chris Wilson in his post on compatibility and IE8. He links to Aaron Gustafson’s new article on the issue, and...

Excerpt from Ajaxian at

One of the things that worries me about the proposed implementation (this has nothing to do with the actual idea itself, for which I have my own opinion, and which I will not rehash here) is the precedence of HTTP headers versus META tags. The ALA article states that, “For example, it is possible to set a baseline lock on a whole site using the header method and then override that header on individual pages, as needed, using the meta element.” This is simply not how it works for other HTTP headers; the Content-type/encoding header is one that particularly pops into mind. For this header, the HTTP header takes precedence over META; the reason for this decision is to prevent the browser from having to parse the document until the META section, find out the document is in a different encoding, throw out the parse tree, and start again. X-UA-Compatible completely reverses this, and will add more confusion to an already muddled situation with Content-type (a lot of websites serve HTTP headers that contradict their page’s meta parameters).

Sam, your specific concerns have to do with HTML fragments that need to be remixed outside of the original document. I’d say, “Forget about it!” This would mean Internet Explorer would need to support multiple engines for one page, which compounds what already seems to be a formidable maintenance problem. Additional, practical considerations dictate content inside these fragments likely would not care too much about the rendering engine (MySpace might be a formidable exception, but RSS feeds certainly shouldn’t need to worry about it).

Posted by Edward Z. Yang at

I’d say, “Forget about it!”

Why do that only in the context of feeds and social networking sites?

Posted by Sam Ruby at

A Simple Solution For IE8

The web is bustling with dialog about IE8’s proposed behaviors for selecting the engine that should render a page. Sam Ruby proposed a simple .htaccess addition that would make the added complexity disappear. And while the use of the “IE=edge”......

Excerpt from Full Speed at

IE8 e Compatibilidade

Ronaldo Ferraz - IE8 e Compatibilidade: Em última instância, a mudança demonstra um interesse por parte da Microsoft em lidar com problemas de compatibilidade e não fazer com que tudo pare de funcionar quando uma nova versão do IE sair. Nesse ponto,...

Excerpt from LSDR.net at

[from deusx] Sam Ruby: Best Standards Support

“Accordingly, I’ve implemented the following in my .htaccess file”...

Excerpt from del.icio.us/network/bkerr at

IE8 versioning snowstorm

keeping track on what is being said about IE8 and opt-in versioning mechanism....

Excerpt from W3C Q&A Weblog at

A Simple Solution For IE8

The web is bustling with dialog about IE8’s proposed behaviors for selecting the engine that should render a page. Sam Ruby proposed a simple .htaccess addition that would make the added complexity disappear. And while the use of the “IE=edge”......

Excerpt from Full Speed at

My suggestion would be for IE8 to (in addition) add application/xhtml+xml to it’s accept-type header, and use the latest and greatest rendering engine for this mime-type by unchangeable default.

Posted by Robbert Broersma at

Standard storm

First read this (although you probably have already): Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8 Then take a look at these: Broken (If you only read one of these, make it this one) From Switches to Targets: A Standardista’s...

Excerpt from David Emery Online at

Shelley - it’s easy to code to standards when you design a new website. What if you’re the webmaster of a 10,000 page dynamic website that’s been going for 5 years, are you supposed to fix it all so it works in the latest, standards-compliant browser? The IEBlog mentions how IE7 broke half of the top 100 websites. Coding workarounds is painful, but I can’t imagine how much more painful it must be to fix existing implementations.

Sam - considering most MySpace is coded by novices for people who know nothing about HTML, and consequently, most MySpace profile pages with third party templates look absolutely atrocious or simply don’t work at all in standards compliant browsers, I fail to see why this is a problem ;) Your point about mashups is more valid. Shouldn’t mashups communicate with XML then format the content on the “mashing” server, though? I thought that was what web services were all about...

Posted by Dave Clayton at

Mistakes, Sadness, Regret

There were several announcements yesterday. First: The W3C finally got around to publishing one of the drafts of the HTML5 spec as a “first public working draft” (a misnomer if ever there was one, given the history of HTML5). This is news for one...

Excerpt from Hixie's Natural Log at

Dave, you actually make the best point of having the switch Microsoft has proposed, but in inverse. If you have an old web site that relies on rendering bugs in Internet Explorer 6 or even 7, that’s a problem between you and Microsoft. So you and Microsoft should find a solution. The solution can be a switch like this, but instead of using it to opt in to standards, it should be used to opt out.

Instead of fixing each and every one of those 10.000 web pages to actually follow web standards, you can add whatever Microsoft wants you to add to say “these pages are unfortunately targeted at Internet Explorer version so and so”. That way, Microsoft proves its commitment to web standards by forcing people to opt out instead of in and renders all newly created web pages in standards mode. Now and for all eternity.

After all, those who code for, with and by web standards don’t target a specific rendering engine, so why on earth would they want to add a rendering engine target switch? It makes no sense. Those targeting rendering engines and opting out of following and using web standards should be the ones using such a switch, not everyone else.

Posted by Asbjørn Ulsberg at

Internet Locker

Internet Explorer aura un système pour activer leur nouveau modèle de rendu dans sa version 8 sans pour autant que les sites précédents ne cessent d’être aussi “jolis” dessus. Il s’agit d’utiliser une balise meta qui...

Excerpt from Sunfox at

Sam Ruby: Best Standards Support

deusx : Sam Ruby: Best Standards Support - “Accordingly, I’ve implemented the following in my .htaccess file” Tags : apache ie8 msft standards webdev...

Excerpt from HotLinks - Level 1 at

Microsoft’s “Super Standards” Mode: Important Facts

The IEBlog let the world know how you’re going to have to opt in for their third (and counting) rendering mode that IE8 will support. You know, the one that should support CSS2 the way other browsers already do without such a mode. Put the...

Excerpt from Something Witty Goes Here at

Chris Wilson : If you (the page developer) really want the best standards support IE8 can give, you can get it by inserting a simple element. Aaron gives more details on this in his article . I’ve implemented the following in my .htaccess file:...

Excerpt from Tailrank: Posts for 'http://planetatom.net' at

IE8 and versioning - very worrying developments

I am not a fan of targeting browser versions. Nor am I a fan of the “opt-out” proposal. I am also unhappy about the idea about going back and adding a new meta element to every site I have done. It seems many others aren’t happy...

Excerpt from maxdesign.com.au at

HTML5 Shiv

Assuming that it’ll be a while before most browsers attempt to implement most of HTML 5 (a perfectly reasonable assumption) we need to start thinking of ways to tackle the creation and rendering of HTML 5 components in the meantime. Obviously, using...

Excerpt from John Resig at

Asbjørn:

So retroactively targetting old browser engine versions on every website we’ve designed is a better idea somehow? I respectfully disagree. You should never have to change old code to keep up with new updates to the platform you’re writing for. Of course in the real world, backwards compatibility is rarely flawless, but it’s the principle that matters.

At the end of the day it’s about practicalities, which is something some of the standards-at-all-costs people seem to be forgetting. If I run a business, I want the least work for the best outcome.

Changing all of my old websites is not cost effective.

Continuing the nightmare of endless situational hacks, fixes, tweaks and workarounds is also a massive waste of resources.

Adding one meta tag to every new page I add is the simplest, cheapest solution.

Standards are great, idealism has its place, but the bottom line is more important.

Posted by Dave Clayton at

Changing all of my old websites is not cost effective.

Ian Hickson noted that people from Opera, from Mozilla (continued), from Webkit, and even from the WaSP, and from the community as a whole (if the comments on Slashdot and other sites are representative) have done the analysis and come to a different conclusion.

Testing for compatibility for each specific browser version for each browser for each web page on the internet and inserting specific annotations recording the results (and thereby possibly changing the results if less popular browsers find that they are in the position of having to implement each others quirks mode) is also not cost effective.

At the end of the day, the conclusion seems to be that somehow Microsoft is special and deserves to handled uniquely.  Standards are things everybody else implements.  If you want to play with Microsoft, you do so on their terms.

That appears to be the bottom line.

Posted by Sam Ruby at

Un altro passo verso HTML 5

Come prontamente segnalato da Giacomo Dotta, ieri, su Webnews, il W3C ha pubblicato la prima bozza pubblica della specifica HTML 5 . La notizia ha certamente un suo interesse perché il marchio di working draft ufficiale del W3C segna una tappa...

Excerpt from edit at

Getting HTML 5 styles in IE 7+

Btw, if you want CSS rules to apply to unknown elements in IE, you just have to do document.createElement(elementName). This somehow lets the CSS engine know that elements with that name exist. This was uttered by Sjoerd Visscher innocently on a...

Excerpt from Ajaxian at

Ok, the Mozilla blog articles were a lot more informative than a lot of other rants I’ve read about this, and makes some good points. I just wish people wouldn’t always assume everything Microsoft does is to serve their own interests. If the impact of IE 8 rendering in full standards mode on workaround-packed sites is minimal then fair enough. I’m all for interoperability - however I can get it ;)

Posted by Dave Clayton at

IE, HTML5, createElement

IE, HTML5, createElement...

Excerpt from IMfO.ru - News at

Microsoft might change the behavior of the “edge” value in the future, so I would guess a big integer (or even a “small” integer > 12) will do the job better?

Posted by Grey at

Monumental week for the Web

I cannot think of a week for the Web in all of the years that I have been a Web developer. Let’s go over the highlights. Ten years of Mozilla — I know that this is relatively minor, but it is worth pointing out that it has been 10 years...

Excerpt from Brian LePore (POWRSURG)'s personal blog at

HTML5 Shim in IE

There’s been something that cropped up as of late thanks to a comment made by Sjoerd Visscher and expanded on further by John Resig here … it seems that by using document.createElement() for a previously unknown tag makes IE start...

Excerpt from James Carr at

Journal Notes

I love it when a plan comes together. Matt Terenzio : “Why we wouldn’t use XMPP as the basis for a decentralized microblogging platform?” XMPP is getting on the scale radar - at last. Dave Winer has picked up on the idea , despite rejecting it...

Excerpt from Bill de hOra at

As usually the problem is with Microsoft keeping us all in the dark with scarcely any information on the features of IE8. Adopting the new switch mechanism in perhaps not a perfect solution but a good temporary one. Of course it would be better if they decided to fully adopt the standards. I’m also curious who and how will store the acronyms of all the user agents (WASP perhaps?)

Posted by Daniel Lewis at

I’ve read opinions that the switch solution offered by Microsoft is better than chaotic problems with proper pages rendering, but I don’t find it a convincing argument. Accepting something just because the alternative is even worse is not a way we should think. The fact that there are worse ideas and solutions doesn’t make the one proposed by Microsoft more sensible. Let’s face it, full adoption of web standards by IE8 would resolve this issue completely.

Posted by Sebi at

IE 8 Something; Web Indigestion Ensued

C’mon, I can’t believe I am the first person to go with the “8"→"Ate” pun. It seems IE8 will......

Excerpt from Jeremy Smith's blog at

INTERNET EXPLORER 8 E O MODO SUPER STANDARD

Primeiramente, não vou repetir aqui o que já foi dito em milhares de sites por aí, portanto, se quiserem mais informações sobre esse assunto que rolou durante essa semana no mundo dos WebStandards, é bom dar uma olhada...

Excerpt from Pinceladas da Web - Movido a XHTML, CSS e WebStandards at

This Week's Semantic Web

Selected links related to Semantic Web technologies for the week ending 2008-01-28, all weeks . Also available in RDF as linked data or via GRDDL . In the Media Podcast: Jon Udell interviews Richard Wallis on libraries, the Talis and the Semantic...

Excerpt from Planet RDF at

Saved By: Daniel Morrison | View Details | Give Thanks Tags: browsers , ie8 , wasp , meta , X-UA-Compatible...

Excerpt from Ma.gnolia: Daniel Morrison's Bookmarks Tagged With "X-UA-Compatible" at

Internet Explorer 8 round-up

My take: On IE8: Pragmatic and practical, but I still don’t like it UPDATES: Microsoft versioning: accessibility implications What Internet Explorer’s change means for accessibility. Best Standards Support Sam Ruby offers a server-side...

Excerpt from Tiffany B. Brown at

Internet Explorer 8 e o Modo Super Standard

Se você é um desenvolvedor antenado já viu a última da Microsoft, não viu? Pois bem, o que você achou disso? Ficou boiando sobre o assunto, dê uma olhada nos seguintes links: A List Apart: Beyond DOCTYPE: Web Standards, Forward Compatibility, and...

Excerpt from MX masters - Sua central do conhecimento na web at

Current confusion most probably arises from lame Microsoft’s policy of not releasing any specific and detailed information on the features of their new browser, so noone really seems to know how cetrain things will work. And of soure we all tend to be a bit sceptical if they will work correctly (this is IE after all). It seems to me that the switch feature will be good enough to temporarily solve the problem, but eventually Microsoft will have to conform to web standards if they want their browser to be recognized by the web deveopers community.

Posted by Andrea Creviola at

I’m not really convinced by the solution adopting the doctype switch device. It’s ludicurous to believe that older versions of documents can be displayed solely be means of a single rendering mode. Such practice was applied to older versions of Word documetns and nothing good came out of it (you can read about here: [link] ). Why won’t they simply conform to the web standards?

Posted by Barney Finnegan at

Fixing <abbr> in IE with one line of JavaScript

One positive side-effect of the recent sugar storm surrounding the announcement that IE8 will, as things stand, require developers to opt in to its new standards mode is this comment by Sjoerd Visscher , which I read several days ago but have been...

Excerpt from Cottleston Pie at

Sjoerd Visscher’s revelation

Via Sam Ruby, we are pointed to this in the comments at Intertwingly: Btw, if you want CSS rules to apply to unknown elements in IE, you just have to do document.createElement(elementName). This somehow lets the CSS engine know that elements with...

Excerpt from Closer To The Ideal at

IE-hate

There seems to be two camps on how IE8 should behave: MS & Joel: IE8 should be broken in different ways to previous IE releases, but it should nearly work on IE specific sites. Everyone else: It should be standards compliant, if sites built to work...

Excerpt from Feet up! : at

How to style unknown elements in IE

Two days ago I posted what I thought was just a little tip on the weblog of Sam Ruby . He was trying to style the new elements from HTML5 in Internet Explorer. Here at Xopus we have known for several years (since about 2002 or 2003) that you have...

Excerpt from Xopus - Developer Blog at

HTML5 и IE

Оказывается, есть немного кривой, но способ заставить IE показывать незнакомые ему теги в глобальном namespace ! В частности, это поможет уже сейчас использовать семантические теги из HTML5. Решение основано на интересном хаке : Btw, if you want CSS...

Excerpt from Bolk site at

Supporting New Elements in IE

How to make Internet Explorer behave with new and unknown elements introduced in HTML5....

Excerpt from The WHATWG Blog at

The year of HTML 5

Let’s kick this year off with a prediction: by the end of 2009, you will be writing HTML 5. To break the ice and lead the way, I have converted this site to HTML 5. Read on for some useful resources to get you started....

Excerpt from Lensco.be at

5 for 4

Safari 4 went public beta today, and its site is in HTML5. Welcome to the mainstream, , , , , and . Apple uses the document.createElement trick to force IE to start accepting them as stylable container elements. (This was apparently discovered just...

Excerpt from Waffle at

Safari 4, HTML5, and Legacy Browser Testing

Jesper’s beat me to the punch, but the headline says it all. To supporters of HTML5, the most important part of Safari 4 is the first line of it’s official web site: <!DOCTYPE html> It uses a trick with document.createElement to...

Excerpt from Phil Nelson at

HTML5 - finally here?

The world of the web is changing, perhaps more now than ever. With vast numbers of people now regularly online the web is no longer the province of geeks and academics, but a valuable part of everyday life for many. So it stands to reason that the...

Excerpt from stillbreathing.co.uk at

IE8 Best Standards Support

You can also add the <meta http-equiv=”X-UA-Compatible” content=”IE=edge” /> edge value to your http headers by adding it to your .htaccess files like this: BrowserMatch MSIE best-standards-support Header set X-UA-Compatible IE=edge...

Excerpt from Broerse Blog at

Looks like you’ve started a cargo cult: [link]

Posted by Henri Sivonen at

(To be fair, it’s not a very big cult so far - the 46 pages are all from one system, running on tournamentsoftware.com and toernooi.nl)

Posted by Philip Taylor at

Amusingly, I no longer serve such a header.

Posted by Sam Ruby at

如何在 IE 中使用 HTML5 元素

Sjoerd Visscher 发现了一个简洁的 方法 让样式在 IE 中作用到未知的元素上——仅需 JS 创建此未知元素即可: document.createElement(elementName) 同理(对于 IE 来说 HTML5 元素即是未知元素),该方法也可顺延到 HTML5 的元素上(详细见:John Resig 写的 《HTML5 Shiv》 一文): <html> <head> <style>section { color:...

Excerpt from PlanABC - 怿飞’s Blog at

如何在 IE 中使用 HTML5 元素

Sjoerd Visscher 发现了一个简洁的 方法 让样式在 IE 中作用到未知的元素上——仅需 JS 创建此未知元素即可: document.createElement(elementName) 同理(对于 IE 来说 HTML5 元素即是未知元素),该方法也可顺延到 HTML5 的元素上(详细见:John Resig 写的 《HTML5 Shiv》 一文): <html> <head> <style>section { color:...

Excerpt from PlanABC - 怿飞’s Blog at

How to get HTML5 working in IE and Firefox 2

HTML5 may be the latest and greatest technology, but some browsers don’t have native support for the new semantic elements. Let’s forget for a minute about the even sexier functionality that the elements can bring, such as full control...

Excerpt from html5doctor at

Disfruta de HTML5 en Internet Explorer y Firefox 2

Aunque el HTML5 está lejos, la gente ya está empezando a desarrollar cosillas usando sus nuevas capacidades. Y es que cada vez más los navegadores lo están adoptando, aunque aún es muy pronto para poder usarlo libremente sin preocuparnos de...

Excerpt from aNieto2K at

IE8でのHTML5要素有効化あれこれ :: 開発日誌,JavaScript

もう7月も終わりですね、martinです。相変わらず時の流れは速いもので。 このサイトのブログの基本テーマ(スキン)「Basic」では、試験的にHTML5を導入しています。HTML5では新しい要素がいくつか追加されていますが、IE9未満の......

Excerpt from ppBlog official at

Comment faire fonctionner le HTML5 dans IE et Firefox

Même si HTML 5 est une technologie récente et fantastique, certains navigateurs ne supportent pas nativement les nouveaux éléments sémantiques. Pour le moment, oublions les fonctionnalités vraiment séduisantes comme le contrôle complet de l’élément...

Excerpt from Docteur HTML5 at

使用 HTML5 Shiv 让 IE 支持 HTML5

现在越来越多浏览器已经实现支持 HTML5,其中 iPad 上的 Safari 浏览器对 HTML5 支持就非常完美,所以我们做的 iPad 导航就是完全用 HTML5 写的。 IE 无法渲染 HTML5 样式 IE 的用户完全不是我们的目标用户,但是总有人有人说我们网站显示的乱七八糟,很烂,因为 IE 不知道如何给不能识别的标签或者元素渲染 CSS,比如 <header> 这些 IE 无法识别的标签,我们在 CSS 中定义的样式,IE 就无法渲染,所以还是决定让 iPad...

Excerpt from 我爱水煮鱼 at

HTML 5 no IE e Firefox 2 com html5.js

Então, você é um designer, HTMLer ou programador antenado e preocupado com os padrões web, correto? E mal vê a hora de estruturar seu HTML de uma forma mais semântica com o html 5, estou certo? Mas, como você deve saber, só agora é que o IE 9, ainda...

Excerpt from Blog do Renato, o Louro at

Supporting HTML5 elements without JavaScript

HTML5 is the newest standard for HTML development, it has a range of additional features that will change the way we interact with the web. This is great for web development, there is a problem though, older browser versions specifically IE 6, 7 and...

Excerpt from George Paterson at

HTML5 Elements in Internet Explorer

The HTML5 specification is still a working draft and it is estimated that it could be 2022 before it becomes a W3C Recommendation, however HTML5 is ready to use today! A HTML5 test page displayed correctly by default in Firefox 3 The Caveat From a...

Excerpt from Wayne Moir at

[zt]使用 HTML5 Shiv 让 IE 支持 HTML5

现在越来越多浏览器已经实现支持 HTML5,其中 iPad 上的 Safari 浏览器对 HTML5 支持就非常完美,所以我们做的 iPad 导航就是完全用 HTML5 写的。 IE 无法渲染 HTML5 样式 IE 的用户完全不是我们的目标用户,但是总有人说我们网站显示的乱七八糟,很烂,因为 IE 不知道如何给不能识别的标签或者元素渲染 CSS,比如<header> 这些 IE 无法识别的标签,我们在 CSS 中定义的样式,IE 就无法渲染,所以还是决定让 iPad...

Excerpt from interUI at

The Story of the HTML5 Shiv

Heard of Sjoerd Visscher? I would venture to guess you have not; however, what he considered a minor discovery of his is at the foundation of our ability to use HTML5 today. Back in 2002, In The Hague, Netherlands, Mr. Visscher was attempting to...

Excerpt from Paul Irish at

JavaScript fallback for HTML5 elements in non-supported browsers

Overview Most browsers support the new HTML5 elements already . However, Internet Explorer versions 8 and below do not recognize the new elements, such as <section> and <article> , and don’t allow them to be styled with CSS by default....

Excerpt from drupal.org - Themers at

@Shelly T.I.IE (That is internet explorer) still hovering around 50% browser profiles you can’t ignore IE.
It can be handled conditionally and just needs to be part of the scope of your project :(

Posted by G at

Creating HTML5 page with CSS3

In this tutorial, I will be creating web page using HTML5 with its new markups or tags and CSS3 with its features as mentioned in previous CSS3 posts so far. Introduction Starting with the HTML page, as we all know that HTML has evolved a lot from...

Excerpt from All Design StuffsAll Design Stuffs | All Design Stuffs at

status changed; owner set

owner set to rwaldron status changed from new to assigned For reference:   [link] and   [link]...

Excerpt from jQuery Core: Ticket #9496: Non-inline styles fail when appending multiple made-up elements in IE < 9 at

How to make Internet Explorer Render HTML5 without JavaScript

The excitement surrounding HTML5 is gathering pace, and the benefits of using it are starting to be felt. And Why not? It is after all “the way of the future”. I for one was very keen to make the leap to HTML5, and certainly all the modern browsers...

Excerpt from Rob Crowther at

如何让IE支持HTML5新元素

我们使用新的HTML5元素时,在其它浏览器中能表现良好的标签(比如Section,article,header和footer)对IE浏览器是个挑战.问题的原因来在IE浏览器的解析机制,这些不能不识别的标签元素导致文档对象的错误展现。 为了说明这个问题,请看下面的简短代码: <body> <section>

This is an example

</section> </body>

...

Excerpt from HTML5研究小组 at

html5shim vs html5shiv

JavaScript Advent Calendar 2011 (オレ標準コース) 12日目の id:t32k です。去年も参加しましたがなんでもありと聞いて今年も懲りずに参加! はじめに言っておきますが、html5sh [...]...

Excerpt from MOL at

Add your comment