Transition from Legacy to Native rendering - (was Re: [whatwg] repetition model)

Ian Hickson ian at
Mon Jun 21 07:16:09 PDT 2004

On Mon, 14 Jun 2004, Hallvord Reiar Michaelsen Steen wrote:
> I imagine the script libraries should be written with this in mind and
> themselves check whether the UAs support WebForms 2 natively.
> Something like..
> if(! (document.implementation && document.implementation.hasFeature
> && document.implementation.hasFeature('WebForms', '2.0') ) ){
>     // create SCRIPT element or write SCRIPT tag linking in the WF2
>     // JavaScript libraries here
> }
> If it gets implemented first in Opera and Mozilla and they do not add
> support for CSS behaviours it is of course tempting to just use a CSS
> behaviour property for IE. Even so the script library itself should
> probably use hasFeature to avoid crashing with a native
> implementation.
> Ian, perhaps one ought to mention this somewhere if you write
> something about requirements for legacy UA-libraries?


I don't really know what a good solution is. hasFeature() doesn't really
work; since it is highly likely that WF2 will be implemented piecemeal,
like all other specs. (I have put a hasFeature string into the spec, but I
don't think it is enough.)

I'm open to suggestions.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

More information about the whatwg mailing list