In our application, we want to do the following:
1) Keep a hidden field in a form with a specified id
2) At a certain point in the app, change the value of the field (or hide it
completely using setVisible(false)).
3) In the onClick javascript event of a link, check either the existence of
the
On Wed, Oct 20, 2010 at 12:14 PM, drf davidrfi...@gmail.com wrote:
In our application, we want to do the following:
1) Keep a hidden field in a form with a specified id
2) At a certain point in the app, change the value of the field (or hide
it
completely using setVisible(false)).
3) In
In my opinion; wicket doesn't mess with the id attribute till you tell it
to. There are multiple means to change the id. but by default the id is not
touched.
Note: wicket:id is not the same as id of the HTML DOM element. So if you
define an id in the markup it should stick.
As per your quote::
On Wed, Oct 20, 2010 at 12:26 PM, Arjun Dhar dhar...@yahoo.com wrote:
In my opinion; wicket doesn't mess with the id attribute till you tell it
to. There are multiple means to change the id. but by default the id is not
touched.
Note: wicket:id is not the same as id of the HTML DOM element.
only if you or something else calls setoutputmarkupid(true)
-igor
On Wed, Oct 20, 2010 at 10:30 AM, Jeremy Thomerson
jer...@wickettraining.com wrote:
On Wed, Oct 20, 2010 at 12:26 PM, Arjun Dhar dhar...@yahoo.com wrote:
In my opinion; wicket doesn't mess with the id attribute till you tell it
@Jeremy : my bad then.
I've never seen the id's come on their own unless I do setmarkupId(true) or
add it by SimpleAttributeModifier() or tag.put(id, ...) in
onComponent(Tag). I guess i need to check it out again.
thanks.
--
View this message in context:
On Wed, Oct 20, 2010 at 12:54 PM, Arjun Dhar dhar...@yahoo.com wrote:
@Jeremy : my bad then.
I've never seen the id's come on their own unless I do setmarkupId(true)
As Igor pitched in, yes, it will only change *if* you (or something else
like any ajax behavior) calls
