[ https://issues.apache.org/jira/browse/WICKET-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429057#comment-13429057 ]
Carl-Eric Menzel commented on WICKET-4697: ------------------------------------------ Yes, but I don't think it would make sense for a WebMarkupContainer to start autolinking based on its attributes. Since you can't add any children to an <img> tag anyway I think it would make perfect sense to use Image instead of WMC here. And then Image could be improved to handle the src attribute. > Autolinking not working as soon as component gets a wicket:id > ------------------------------------------------------------- > > Key: WICKET-4697 > URL: https://issues.apache.org/jira/browse/WICKET-4697 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 1.5.7 > Reporter: Matthias Keller > > While migrating from 1.4.X, we encounter a lot of pages having an image with > a relative URL set in the HTML, for example <img src="img/logo.gif"/>. > Now on some pages, those images need to be references, mainly to alter the > visibility logic or add an attribute modifier of some kind. Now as soon as we > do > <img wicket:id="logo" src="img/logo.gif"/> > and add it using add(new WebMarkupContainer("logo")) , autolinking does not > work anymore and the src is left as-is. > Moving all sources to the java files and use ContextImage etc is no real > option as this would be a *lot* of work and wouldn't make the html readable > anymore as it would become hard to find all references to the images and also > isn't logical to have the URL in the java files even though it's static and > doesn't change. -- 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