You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by manuelbarzi <ma...@gmail.com> on 2011/09/28 18:18:34 UTC
pretty strange behavior with TextArea containing remaining output
html code inside
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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by manuelbarzi <ma...@gmail.com>.
should a single closed textarea tag be a problem? neither html editor
nor wicket markup validation complains about it.
.
On Wed, Sep 28, 2011 at 6:26 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> sounds like a problem with your html...
>
> -igor
>
>
> On Wed, Sep 28, 2011 at 9:18 AM, manuelbarzi <ma...@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by Igor Vaynberg <ig...@gmail.com>.
sounds like a problem with your html...
-igor
On Wed, Sep 28, 2011 at 9:18 AM, manuelbarzi <ma...@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by Igor Vaynberg <ig...@gmail.com>.
wicket can be used for any xml-based markup, not just html...
-igor
On Thu, Sep 29, 2011 at 1:16 AM, Martin Grigorov <mg...@apache.org> wrote:
> Wicket uses (custom) XML parser when loading the HTML.
> <textarea/> is a valid xml and thus it doesn't fail.
>
> HTML validator is a dirty job because different browsers implement the
> specs differently ... :-/
>
> On Thu, Sep 29, 2011 at 10:02 AM, manuelbarzi <ma...@gmail.com> wrote:
>>> Wicket doesn't act as (X)HTML validator. It never did.
>>
>> but if you forget some closing tag, </tr> for instance, you might be
>> sure it will complain... then why not validating other tags too, and
>> fully validate (x)html.
>>
>>
>>
>> On Thu, Sep 29, 2011 at 9:56 AM, Martin Grigorov <mg...@apache.org> wrote:
>>> Wicket doesn't act as (X)HTML validator. It never did.
>>> You may use https://github.com/dashorst/wicket-stuff-markup-validator for that
>>>
>>> On Thu, Sep 29, 2011 at 9:53 AM, manuelbarzi <ma...@gmail.com> wrote:
>>>> 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 <mg...@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 <ma...@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 <ig...@gmail.com> wrote:
>>>>>>> file a jira issue
>>>>>>>
>>>>>>> -igor
>>>>>>>
>>>>>>> On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <ma...@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 <ig...@gmail.com> wrote:
>>>>>>>>> per html spec textarea must have a closing tag...
>>>>>>>>>
>>>>>>>>> -igor
>>>>>>>>>
>>>>>>>>> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>>>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Martin Grigorov
>>>>> jWeekend
>>>>> Training, Consulting, Development
>>>>> http://jWeekend.com
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Martin Grigorov
>>> jWeekend
>>> Training, Consulting, Development
>>> http://jWeekend.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by Martin Grigorov <mg...@apache.org>.
Wicket uses (custom) XML parser when loading the HTML.
<textarea/> is a valid xml and thus it doesn't fail.
HTML validator is a dirty job because different browsers implement the
specs differently ... :-/
On Thu, Sep 29, 2011 at 10:02 AM, manuelbarzi <ma...@gmail.com> wrote:
>> Wicket doesn't act as (X)HTML validator. It never did.
>
> but if you forget some closing tag, </tr> for instance, you might be
> sure it will complain... then why not validating other tags too, and
> fully validate (x)html.
>
>
>
> On Thu, Sep 29, 2011 at 9:56 AM, Martin Grigorov <mg...@apache.org> wrote:
>> Wicket doesn't act as (X)HTML validator. It never did.
>> You may use https://github.com/dashorst/wicket-stuff-markup-validator for that
>>
>> On Thu, Sep 29, 2011 at 9:53 AM, manuelbarzi <ma...@gmail.com> wrote:
>>> 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 <mg...@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 <ma...@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 <ig...@gmail.com> wrote:
>>>>>> file a jira issue
>>>>>>
>>>>>> -igor
>>>>>>
>>>>>> On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <ma...@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 <ig...@gmail.com> wrote:
>>>>>>>> per html spec textarea must have a closing tag...
>>>>>>>>
>>>>>>>> -igor
>>>>>>>>
>>>>>>>> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Martin Grigorov
>>>> jWeekend
>>>> Training, Consulting, Development
>>>> http://jWeekend.com
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by manuelbarzi <ma...@gmail.com>.
> Wicket doesn't act as (X)HTML validator. It never did.
but if you forget some closing tag, </tr> for instance, you might be
sure it will complain... then why not validating other tags too, and
fully validate (x)html.
On Thu, Sep 29, 2011 at 9:56 AM, Martin Grigorov <mg...@apache.org> wrote:
> Wicket doesn't act as (X)HTML validator. It never did.
> You may use https://github.com/dashorst/wicket-stuff-markup-validator for that
>
> On Thu, Sep 29, 2011 at 9:53 AM, manuelbarzi <ma...@gmail.com> wrote:
>> 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 <mg...@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 <ma...@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 <ig...@gmail.com> wrote:
>>>>> file a jira issue
>>>>>
>>>>> -igor
>>>>>
>>>>> On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <ma...@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 <ig...@gmail.com> wrote:
>>>>>>> per html spec textarea must have a closing tag...
>>>>>>>
>>>>>>> -igor
>>>>>>>
>>>>>>> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Martin Grigorov
>>> jWeekend
>>> Training, Consulting, Development
>>> http://jWeekend.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by Martin Grigorov <mg...@apache.org>.
Wicket doesn't act as (X)HTML validator. It never did.
You may use https://github.com/dashorst/wicket-stuff-markup-validator for that
On Thu, Sep 29, 2011 at 9:53 AM, manuelbarzi <ma...@gmail.com> wrote:
> 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 <mg...@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 <ma...@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 <ig...@gmail.com> wrote:
>>>> file a jira issue
>>>>
>>>> -igor
>>>>
>>>> On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <ma...@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 <ig...@gmail.com> wrote:
>>>>>> per html spec textarea must have a closing tag...
>>>>>>
>>>>>> -igor
>>>>>>
>>>>>> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by manuelbarzi <ma...@gmail.com>.
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 <mg...@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 <ma...@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 <ig...@gmail.com> wrote:
>>> file a jira issue
>>>
>>> -igor
>>>
>>> On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <ma...@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 <ig...@gmail.com> wrote:
>>>>> per html spec textarea must have a closing tag...
>>>>>
>>>>> -igor
>>>>>
>>>>> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by Martin Grigorov <mg...@apache.org>.
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 <ma...@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 <ig...@gmail.com> wrote:
>> file a jira issue
>>
>> -igor
>>
>> On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <ma...@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 <ig...@gmail.com> wrote:
>>>> per html spec textarea must have a closing tag...
>>>>
>>>> -igor
>>>>
>>>> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by manuelbarzi <ma...@gmail.com>.
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 <ig...@gmail.com> wrote:
> file a jira issue
>
> -igor
>
> On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <ma...@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 <ig...@gmail.com> wrote:
>>> per html spec textarea must have a closing tag...
>>>
>>> -igor
>>>
>>> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by Igor Vaynberg <ig...@gmail.com>.
file a jira issue
-igor
On Wed, Sep 28, 2011 at 9:52 AM, manuelbarzi <ma...@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 <ig...@gmail.com> wrote:
>> per html spec textarea must have a closing tag...
>>
>> -igor
>>
>> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by manuelbarzi <ma...@gmail.com>.
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 <ig...@gmail.com> wrote:
> per html spec textarea must have a closing tag...
>
> -igor
>
> On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by Igor Vaynberg <ig...@gmail.com>.
per html spec textarea must have a closing tag...
-igor
On Wed, Sep 28, 2011 at 9:25 AM, manuelbarzi <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by manuelbarzi <ma...@gmail.com>.
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 <ma...@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 <ma...@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: pretty strange behavior with TextArea containing remaining output
html code inside
Posted by manuelbarzi <ma...@gmail.com>.
TextArea is one-self-closed tag <.../>.
should TextArea two-opening-closing tags <...>...</...> work fine.
On Wed, Sep 28, 2011 at 6:18 PM, manuelbarzi <ma...@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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: How to set Cookie on Redirect to URL
Posted by Martin Grigorov <mg...@apache.org>.
Here is what I use to keep the cookies (headers):
public class NonResettingRestartException extends ReplaceHandlerException {
public NonResettingRestartException(final Class<? extends Page<?>>
pageClass, final PageParameters params, final RequestCycle cycle) {
super(createRequestHandler(pageClass, params), true);
Response response = cycle.getResponse();
if (response instanceof IMetaDataBufferingWebResponse) {
IMetaDataBufferingWebResponse bufferingWebResponse =
(IMetaDataBufferingWebResponse) response;
bufferingWebResponse.writeMetaData((WebResponse)
cycle.getOriginalResponse());
}
}
private static IRequestHandler createRequestHandler(Class<?
extends Page<?>> pageClass, PageParameters params) {
return new RenderPageRequestHandler(new
PageProvider(pageClass, params));
}
}
On Thu, Sep 29, 2011 at 12:01 AM, <bh...@actrix.gen.nz> wrote:
> Hi,
>
> How do I add a cookie to a URL redirect response? I started with the
> following class:
>
> public class RedirectToUrlWithHandlerException extends
> ReplaceHandlerException {
> ...
>
> public RedirectToUrlWithHandlerException(final String redirectUrl,
> final int statusCode, final IRequestHandler handler) {
> super(new RedirectRequestHandler(redirectUrl, statusCode){
> @Override
> public void detach(IRequestCycle requestCycle) {
> super.detach(requestCycle);
> handler.detach(requestCycle);
> }
> @Override
> public void respond(IRequestCycle requestCycle) {
> super.respond(requestCycle);
> handler.respond(requestCycle);
> }
> }, true);
> }
> }
>
>
> and in the page:
>
> throw new RedirectToUrlWithHandlerException(targetUrl, new
> IRequestHandler(){
> @Override
> public void respond(IRequestCycle requestCycle) {
> // Set cookie
> cookieUtils.save(name, value);
> }
>
> @Override
> public void detach(IRequestCycle requestCycle) { }
> });
>
> with cookieUtils:
>
> instance.cookieUtils = new CookieUtils(cookieDefaults){
> @Override
> protected void initializeCookie(Cookie cookie) {
> super.initializeCookie(cookie);
> cookie.setPath("/");
> }
> };
>
>
> Still no cookie in the response.
>
> I know this is a tricky issue where older browsers don't always
> cooperate, but the page being redirected to can't set the cookie
> because the cookie is used to transfer information to it.
>
> Many thanks,
>
> Bernard
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
How to set Cookie on Redirect to URL
Posted by bh...@actrix.gen.nz.
Hi,
How do I add a cookie to a URL redirect response? I started with the
following class:
public class RedirectToUrlWithHandlerException extends
ReplaceHandlerException {
...
public RedirectToUrlWithHandlerException(final String redirectUrl,
final int statusCode, final IRequestHandler handler) {
super(new RedirectRequestHandler(redirectUrl, statusCode){
@Override
public void detach(IRequestCycle requestCycle) {
super.detach(requestCycle);
handler.detach(requestCycle);
}
@Override
public void respond(IRequestCycle requestCycle) {
super.respond(requestCycle);
handler.respond(requestCycle);
}
}, true);
}
}
and in the page:
throw new RedirectToUrlWithHandlerException(targetUrl, new
IRequestHandler(){
@Override
public void respond(IRequestCycle requestCycle) {
// Set cookie
cookieUtils.save(name, value);
}
@Override
public void detach(IRequestCycle requestCycle) { }
});
with cookieUtils:
instance.cookieUtils = new CookieUtils(cookieDefaults){
@Override
protected void initializeCookie(Cookie cookie) {
super.initializeCookie(cookie);
cookie.setPath("/");
}
};
Still no cookie in the response.
I know this is a tricky issue where older browsers don't always
cooperate, but the page being redirected to can't set the cookie
because the cookie is used to transfer information to it.
Many thanks,
Bernard
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org