[
https://issues.apache.org/jira/browse/WICKET-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873412#comment-13873412
]
Martin Grigorov commented on WICKET-4697:
-----------------------------------------
The commit that caused the change in the behavior is:
commit 90fdfd0dedf47d2b57c122e9587053e930382221
Author: Juegen Donnerstag <jdonners...@apache.org>
Date: Wed Aug 8 12:41:50 2007 +0000
Until now we identified internally created wicket id's by a leading "_",
e.g. _header. Since this convention is a little bit dangerous, I have extended
ComponentTag to maintain an
git-svn-id: https://svn.apache.org/repos/asf/wicket/trunk@563840
13f79535-47bb-0310-9956-ffa450edef68
> 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
> Assignee: Carl-Eric Menzel
> Attachments: WICKET-4697.zip
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
