- From: Jim Ley <jim.ley@gmail.com>
- Date: Sat, 17 Jul 2004 16:23:26 +0100
On Sat, 17 Jul 2004 16:34:53 +0200, Hallvord Reiar Michaelsen Steen <hallvors at online.no> wrote: > On 15 Jul 2004 at 17:44, Jim Ley wrote: > > > It doesn't work with scripting disabled when you enter "15/7/4" and > > then use the back button after submission, no hint is available to the > > user, even though that is essential to me being able to submit the form. > > I guess most websites would handle this by returning the same form > with error message and extra hints, not like the demo that just tells > you to use the back button. but how does it do this - this is my point, as soon as you want to put a value in the datetime control (and everyone does this when re-displaying a form) you use the ability to put the hint in - despite the fact the hint is more important now, as the user obviously didn't understand it the first time! > Ian should add that. If I'm not mistaken the discussion on the list > concluded that the best option was to check the "type" property of > the input element. It should be "text" if the UA does not support > datetime. So, Ian could add to his onload handler: > > wf2client=(document.forms[0].elements['t1'].type=='datetime'); This has already been discussed, and it's demonstrated that this is not a satisfactory discrimination for testing support for datetime - there's no point just saying it again, I'm certainly not going suddenly to notice that FireFox (for example) all of sudden fails that test. It's a simple fact that the above is not a suitable discriminator for WF2 support. What is? Jim.
Received on Saturday, 17 July 2004 08:23:26 UTC