[
https://issues.apache.org/jira/browse/WICKET-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795257#action_12795257
]
Martin Grigorov commented on WICKET-2650:
-----------------------------------------
As far as I remember expanding of div and span was added to overcome a bug in
Firefox (maybe version 2.x). So Wicket is trying to help the user here.
I don't agree that Wicket should fix developer/webdesigner errors, like <a
href="" ... />. Especially I don't want to see any of my <img /> or <input />
expanded.
There are helper utils in Wicket like devutils' Filter for <img src="" />
(image empty source location) which are there to help me and extending them to
warn me about my coding mistakes would be great.
> Consistently create body for short tags.
> ----------------------------------------
>
> Key: WICKET-2650
> URL: https://issues.apache.org/jira/browse/WICKET-2650
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.0
> Reporter: Maarten Billemont
>
> When the Wicket HTML contains a tag such as <a wicket:id="foo" /> and the
> component bound to that tag uses replaceComponentTagBody to write a string to
> the tag's body, currently nothing happens.
> Either a text node should be added to the component tag and the body written
> to it;
> Or a warning/exception should occur if for some reason it is preferred to not
> let this method succeed when the component tag has no body yet.
> I don't see the use of the latter, so I recommend the former be implemented.
> For now it's just confusing and dangerous. If I give my HTML to a web
> designed and he changes a few empty HTML tags to short tags, I'll never be
> warned, but my output WILL be broken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
