Indeed, it seems that the old value is overriden with the generated value...
In this case, why the markupId do not care about the old value? Wouldn't it
be much better if it would be the same as the original id?
Alex Objelean wrote:
>
> In this case, the designer efforts will be disabled anytime I use an
> ajaxified component, isn't it?
> For instance I have :
>
> <div wicket:id="idForWicket" id="idForDesigner"></div>
>
> in CSS:
>
> div#idForDesigner {
> float: left;
> border: solid red 1px;
> }
>
> in JAVA:
>
> Component component = new MyComponent("idForWicket");
> component.setOutputMarkupId(true);
>
> As the result, the idForDesigner will be overriden with a new generated
> value? Did I understood it right?
>
>
>
--
View this message in context:
http://www.nabble.com/Question-about-OutputMarkupId-tf1883868.html#a5150652
Sent from the Wicket - User forum at Nabble.com.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
