http://blog.mouvedia.com&#65286; web design considerationsMon, 06 Jun 2011 13:18:03 +0200Habari 0.7 http://habariproject.org/http://blog.mouvedia.com/how-to-properly-detect-details-supportBetween version 10.0.603 and 12.0.701 Google Chrome had partial support for the <code>&#60;details&#62;</code> carelessly leaving its rendering <a href="https://bugs.webkit.org/show_bug.cgi?id=51071#c57">for later</a>. <a href="http://mathiasbynens.be/notes/html5-details-jquery#comment-35">Mathias Bynens</a> created a feature test which was too convoluted for my liking. So I've made some research and found a shorter method which use what-I-am-calling correlated feature detection. <pre> if(!("open"in document.createElement("details"))||window.chrome&&window.google&&google.gears) {fallback()} </pre> In the very unlikely edge case that you have installed <a href="http://gears.google.com/" title="removed since version 12.0.702">Gears</a> on Chrome 12+ you would be served the javascript polyfill instead. As a matter of fact Google plans to provide offline support to Gmail using HTML5 <a href="http://www.google.com/support/a/bin/answer.py?hl=en&answer=1308394">this summer</a> which will probably coincide with the first stable release to natively support the <code>&#60;details&#62;</code> element.Mon, 06 Jun 2011 13:18:03 +0200tag:blog.mouvedia.com,2011:how-to-properly-detect-details-support/1307359083http://blog.mouvedia.com/testtestTue, 19 Apr 2011 15:26:08 +0200tag:blog.mouvedia.com,2011:test/1303219568