Timeline for Multivalued form field and validation for empty values
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 18, 2013 at 14:47 | vote | accept | NicoINCH | ||
| Dec 17, 2013 at 15:58 | comment | added | NicoINCH | The user is describing a content for which he has previously specified the attributes list with different properties (such as multivalued), so, as I said, there is no way to specialize according the semantic of the fields. | |
| Dec 17, 2013 at 15:07 | answer | added | Mervin | timeline score: 2 | |
| Dec 17, 2013 at 14:54 | comment | added | DarrylGodden | What is the user describing? | |
| Dec 17, 2013 at 13:38 | history | tweeted | twitter.com/#!/StackUX/status/412939758713970688 | ||
| Dec 17, 2013 at 13:23 | comment | added | Lovis | I see. I thought it would be more like defining a template for later re-use. | |
| Dec 17, 2013 at 13:03 | history | edited | NicoINCH | CC BY-SA 3.0 |
added 123 characters in body
|
| Dec 17, 2013 at 12:53 | comment | added | NicoINCH | As it is a dynamically generated form, there is no way to specialize according the semantic of the fields. | |
| Dec 17, 2013 at 12:46 | comment | added | Lovis | doesn't that depend on the type of the field? if the content can be edited later, leaving it empty might be fine. "hours worked" will be empty in the beginning, but a user might want to enter a value without adding the whole field. | |
| Dec 17, 2013 at 12:32 | comment | added | JonW♦ | Have you got a mockup of your current form - or at least of these type of fields? | |
| Dec 17, 2013 at 12:09 | history | asked | NicoINCH | CC BY-SA 3.0 |