[
https://issues.apache.org/jira/browse/WICKET-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117052#comment-13117052
]
Emond Papegaaij commented on WICKET-4091:
-----------------------------------------
Enabling outputMarkupId from getMarkupId() will help a great deal with
js-integration frameworks, such as WiQuery. WiQuery will render statements such
as $("#id123").plugin(options). For this, it calls getMarkupId to get the
markup id, and also setOutputMarkupId(true), to enable it in the markup. I
think Igor's statement makes sense: if you use the markup id (ie. you call
getMarkupId), you want it in the markup. Or the other way around: what good is
the markup id if it does not show up in the markup?
> 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: 1.6.0
>
>
> 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
