W3C home > Mailing lists > Public > public-html@w3.org > September 2009

Re: <details>

From: Simon Pieters <simonp@opera.com>
Date: Mon, 14 Sep 2009 15:49:55 +0200
To: "Toby Inkster" <tai@g5n.co.uk>, "Anne van Kesteren" <annevk@opera.com>
Cc: "Jeremy Keith" <jeremy@adactio.com>, "Ian Hickson" <ian@hixie.ch>, "HTML WG" <public-html@w3.org>
Message-ID: <op.uz811hw0idj3kv@zcorpandell.linkoping.osa>
On Mon, 14 Sep 2009 15:12:51 +0200, Toby Inkster <tai@g5n.co.uk> wrote:

> This would be a reason to add <script implements> to HTML5. The HTML5
> documentation would define a URI that represents the functionality of
> the <details> element, say:

There's a more robust way supported already:

    if (typeof document.createElement('details').open == 'undefined') {
      // script that implements <details> here
    }


<script implements> seems to be equivalent to hasFeature in its design,  
which is known to be unreliable (see the note about hasFeature in HTML5).

-- 
Simon Pieters
Opera Software
Received on Monday, 14 September 2009 13:50:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:48 GMT