Timeline for When should the "container" form element be used?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2021 at 12:39 | history | wiki removed | avpaderno♦ | ||
| Nov 21, 2015 at 10:43 | history | made wiki | Post Made Community Wiki by avpaderno♦ | ||
| Jul 28, 2015 at 5:05 | history | edited | avpaderno♦ | CC BY-SA 3.0 |
added snippets from the current implementation of the listed functions
|
| Sep 15, 2013 at 19:01 | comment | added | Berdir | Ah, yes, field widgets are always within a language and delta key, within that, they might be repeated, so #tree => TRUE is forced on them, yes. | |
| Sep 15, 2013 at 13:31 | comment | added | jonhattan | Ok, sorry. By casuality I was just adding a container in a field widget form and observed the nesting in $form_state. After your comment, I realized $element['tree'] comes as true. Thanks :) | |
| Sep 15, 2013 at 13:19 | comment | added | Berdir | No, it does not. Only when explicitly specified as #tree => TRUE, the default is FALSE. | |
| Sep 15, 2013 at 9:54 | comment | added | jonhattan | container type also implies a nesting level in form_state's input / values. | |
| Dec 6, 2011 at 23:56 | history | edited | avpaderno♦ | CC BY-SA 3.0 |
added 14 characters in body
|
| S Mar 8, 2011 at 3:24 | history | suggested | avpaderno♦ | CC BY-SA 2.5 |
improved formatting
|
| Mar 7, 2011 at 20:33 | vote | accept | avpaderno♦ | ||
| Mar 5, 2011 at 16:45 | review | Suggested edits | |||
| S Mar 8, 2011 at 3:24 | |||||
| Mar 5, 2011 at 16:13 | history | answered | Berdir | CC BY-SA 2.5 |