-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can we integrate with rich forms and validation? #6
Comments
I think we need a generic form serialization API. |
There are two aspects of this. Getting the data out of a form can be made relatively trivial using an API built on top of http://darobin.github.io/formic/specs/json/. It would likely have to be async (since files may be involved) and it would have to accept the activating control as an optional parameter, but it's not rocket science. In the context of editing there is also the converse: how do we make an editable area participate in form submission. There are various options here. We could have an attribute (possibly reusing the otherwise useless I think that this is a case in which it would prove very useful to prod the community for use cases. |
Can you write this in the form of our other use cases so I can add it to the document? |
I think we should make a generic form participation API, taking this as an important use case. |
Should this issue still be here, or should this be moved to some form-related discussion and spec? I will close for now. Please reopen If I am wrong. |
Originally asked by Robin Berjon, W3C
The text was updated successfully, but these errors were encountered: