W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2006

[whatwg] Detecting Web Forms for future proof scripts?

From: Shawn Wilsher <me@shawnwilsher.com>
Date: Mon, 2 Oct 2006 12:00:02 -0400
Message-ID: <75ab07700610020900n2fbe9e25p8ab13ddcfbbe139b@mail.gmail.com>

Hopefully, you aren't duplicating work that has already been done here:

Granted, this is only for IE, but nearly half of your work is already done then.



On 10/2/06, Ric Hardacre <ric at hardacre.org> wrote:
> I'm attempting to write Javascript scriptlets to emulate some of the Web
> Forms 2.0 spec in HTML 4 documents. Firstly, they obviously need to
> degrade for non-scripting UAs, which is easy enough. Secondly they need
> to check that they're running on a compatible scripting engine, just
> checking for the existence of document.getElementById is the simple way
> (If there are better ways then I'm always open to learning). But I'm
> presented with an issue, suppose for example I wanted to emulate the
> datalist element for a text box. I can use the DOM and some on-the fly
> CSS to build a Javascript emulated datalist, but how would one go about
> ensuring that if/when it encounters a browser that can handle the
> datalist that it does not execute? This is probably quite an open
> question and yes I'm aware of the embedding-a-select-inside-the-datalist
> solution to this particular example, but the general question remains:
> How to script WF2 functionality for current browsers in a way that both
> degrades AND yields to the UA when it can handle the functionality natively?
> Ric Hardacre
> http://www.cyclomedia.co.uk/
Received on Monday, 2 October 2006 09:00:02 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:48 UTC