sure, as you may have read, i already tested on wicket 1.5.0 and renders ok. but from the point of view of validation, a textarea cannot be a single-closed tag, is an "illegal" code, as it goes against the spec (igor).
On Thu, Sep 29, 2011 at 9:49 AM, Martin Grigorov <mgrigo...@apache.org> wrote: > This is improved in 1.5.0. > We expand some HTML elements from <name/> to <name></name> > > You are recommended to upgrade. > > On Thu, Sep 29, 2011 at 9:44 AM, manuelbarzi <manuelba...@gmail.com> wrote: >> tested on wicket 1.5.0 and paradoxically a single-closed textarea tag >> does validate as "legal" too, like in wicket 1.4.17/18, and renders >> correctly, contrary to wicket 1.4.17/18. >> >> issue https://issues.apache.org/jira/browse/WICKET-4094 >> >> >> On Wed, Sep 28, 2011 at 7:30 PM, Igor Vaynberg <igor.vaynb...@gmail.com> >> wrote: >>> file a jira issue >>> >>> -igor >>> >>> On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <manuelba...@gmail.com> wrote: >>>> right. >>>> >>>> may wicket html validation complain in future version for this >>>> particular case. low priority issue... >>>> . >>>> >>>> >>>> >>>> On Wed, Sep 28, 2011 at 6:42 PM, Igor Vaynberg <igor.vaynb...@gmail.com> >>>> wrote: >>>>> per html spec textarea must have a closing tag... >>>>> >>>>> -igor >>>>> >>>>> On Wed, Sep 28, 2011 at 9:25 AM, 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 >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
