» tagged pages
» logout

sorted by: recent | see : popular
Content Tagged with IE + html

My DebugBar | IETester / HomePage

Ce programme pourrait intéresser des webmasters ou testeurs, il permet de prévisualiser et comparer le rendu graphique de différentes versions d'Internet Explorer, sans avoir besoin de les<sep/>

Firefox: del.icio.us/tag/firefox

Using the Right Markup to Invoke Plugins - MDC

Or why IE's handling of <object> is a pain in the ass.

W3C: Del.icio.us W3C Tags

Almost Precedent

thoughtful analysis of "almost standards mode" and IE 8's versioning switch

W3C: Del.icio.us W3C Tags

Quirks mode - Wikipedia, the free encyclopedia

All about how to make browsers use standars mode which complies with W3C standards and quirks mode which allows non standard behavior

W3C: Del.icio.us W3C Tags

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 Sam Ruby thread, and it sent ripples of "huh? really? How come I never know that!" through all of the experts.

This fact means that you the following will show up as red in IE 7:

HTML:
  1.  
  2.  
  3. <style>blah { color: red; }</style>
  4. <script>document.createElement("blah")</script>
  5. </head>
  6. <blah>Hello!</blah>
  7. </body>
  8. </html>
  9.  

This is an example from John Resig as he discusses a HTML 5 shiv. You can see how a JavaScript shim can "implement" some of HTML 5 for us.

We have also gone down this route for some of the HTML 5 spec, and you can indeed do a lot with JavaScript. There are a couple of places where you kinda have to be in the browser to do the right thing.... but these are few and far between.

Sjoerd Visscher just blogged about this and told us how he found it out (back in 2002-ish!):

As far as I can remember we found out about this when we converted the first rendering of the XSL output from a lot of createElement calls to one innerHTML change for performance. This caused our custom elements to no longer be affected by CSS.

Ajax: Ajaxian

Jeffrey Zeldman: In defense of version targeting

Perhaps the most sensible response to the version targeting debacle I've seen so far.

W3C: Del.icio.us W3C Tags

Mistakes, Sadness, Regret (Ian Hickson)

"I recommend not including the meta tag, or, if you are forced to include it, making sure it says 'IE=7', even once IE8 ships."

W3C: Del.icio.us W3C Tags

Quotes (Dean Edwards)

"I won't support any more cruft added to HTML without hearing the reasons. 'Don't break the Web' is a way to befuddle us."

W3C: Del.icio.us W3C Tags

End of line Internet Explorer (Mike Davies)

"Microsoft would do well to learn the lessons of Netscape and realise that Internet Explorer is functionally incapable of both preserving backwards compatibility for its half a billion clients, and supporting web standards. Something has to break."

W3C: Del.icio.us W3C Tags

Meta Madness with X-UA-Compatible

John Resig argues why X-UA-Compatible is an awful idea, especially for non-IE browsers.

Firefox: del.icio.us/tag/firefox

HTMLパーサでXMLの処理は - dhrnameのウェブ日誌

主要HTMLレンダリングエンジンに謎要素を書いた際の終了タグ補完規則の調査。Geckoは未知要素をXML初期値のinlineとして処理し、Operaは無視して最後に帳尻合わせ、かなぁ。

Firefox: del.icio.us/tag/firefox

Page 1 | Next >>