[
https://issues.apache.org/jira/browse/WICKET-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157733#comment-13157733
]
Martin Grigorov commented on WICKET-4091:
-----------------------------------------
With the usage of jQuery in wicket-ajax.js I think the writing of the component
markup id in the final markup can be optional.
We can add target.add(componentWithoutMarkupId, "someValidCssSelector") and
this will produce <component selector="someValidCssSelector">...</component>
and the component(s) which match this CSS selector will be replaced with the
markup of componentWithoutMarkupId.
This will work for any CSS3 selector engine (like Sizzle (jQuery and Dojo),
qwery (Ender), ...);
This way the user will be able to repaint several fragments in the markup with
one shot.
Is this something we want ?
I can see how this can desynchronize the server state with the client view.
> Automate output of markup ids
> -----------------------------
>
> Key: WICKET-4091
> URL: https://issues.apache.org/jira/browse/WICKET-4091
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Igor Vaynberg
> Labels: ajax, markupid
> Fix For: 6.0.0
>
> Attachments: WICKET-4091.patch
>
>
> this is a proposal to remove the rather annoying requirement of having to
> call setoutputmarkupid(true) on components.
> when a user calls getmarkupid() they are showing intent of using that id, so
> if that method is called we should automatically call
> setoutputmarkupid(true). further we should process renderhead() of components
> first - before rendering the components. most calls to getmarkupid() come
> from that method so processing it before rendering the component will toggle
> the correct bit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
