confirmed: a single self-closed textarea tag (<textarea... />) makes rendering fail in this wicket version. it does not complain about textarea markup (neither html editor), but renders it containing the remaining html escaped inside, and setting a closing textarea tag at the end.
only double opening-closing textarea tag (<textarea...>...</textarea>) is supported. On Wed, Sep 28, 2011 at 6:25 PM, manuelbarzi <manuelba...@gmail.com> wrote: > TextArea is one-self-closed tag <.../>. > > should TextArea two-opening-closing tags <...>...</...> work fine. > > > > On Wed, Sep 28, 2011 at 6:18 PM, manuelbarzi <manuelba...@gmail.com> wrote: >> this error happens on this simple composite (wicket 1.4.17): >> >> Page >> |-Panel >> |-Form >> |-TextField >> |-TextField >> |-TextArea >> |-TextField >> |-TextField >> |-Button >> |-Button >> >> when just rendering this simple page (no logic implemented yet), the >> output html (reviewed on chrome and ie) renders ok until the TextArea, >> and then, inside the TextArea content (visible text), there's all the >> remaining of the output markup! >> >> switching TextArea to a simple TextField does render ok. >> >> known bug? >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
