As I said, I am working on a wf2 imnplementation library. I am aware of
the ongoing project (http://code.google.com/p/webforms2/), but it was
more fun doing this on my own. I implemented a whole lot of the spec,
including repetition model.
Everything is not quite mature yet, but I would like to share it with
the world anyway.
http://www.rikkertkoppes.com/thoughts/wf2/
Regards,
Rikkert Koppes
Ian Hickson schreef:
On Tue, 28 Aug 2007, Rikkert Koppes wrote:
I am currently implementing a js library to make wf2 functionality
available to legacy browsers (I know google is doing this too). Some
things that came to mind are:
- when validity flags are not set, should they equal null or false?
False. Is the spec not clear on this?
- this might have been proposed before: consider a reset() method for
form controls and fieldsets
You can already do this reasonably easily; I'm not sure an explicit API is
really that useful. I'll bear it in mind though.
- in this light: consider a clearable or resettable boolean attribute
for inputs, which might display a "clear" button in the field, as seen
in for example the mail filter in thunderbird. This should reset the
control to the default value, ie calling the above reset() method,
example formatting:
+--- legend [x] -------------------+
| |
| +----------------------+ |
| | [x]| |
| +----------------------+ |
+----------------------------------+
which shows a clear button on a fieldset and input field. Note that
Opera's date related fields also have an "none" button, which might be
equivalent of the above
That's just a UI detail. Nothing is stopping UA implementors from
including this kind of UI today.
- are negative years allowed (B.C.)? the datetime description tells me
"four or more digits (0 to 9) representing the year" which implies "no".
use case: hystory questionary
No, negative years aren't allowed. As has been pointed out by others, the
date control isn't really that useful as defined today for
non-contemporary dates. The use case is primarily e-commerce. Historical
cases are far more complex, rarer, and probably need custom UI, and thus
don't really fall in our "80%" target.
Let us know if there's anything else we can do to help with your
implementation! Also, note that there's an implementors mailing list if
you want to discuss implementation-specific details:
http://www.whatwg.org/mailing-list#imps
HTH,
