There seems to be a bug in Internet Explorer in the following scenario ...
(verified in IE 6.0, wicket 1.3.3)
<html>
<head></head>
<body>
<form id="ic"> </form>
<script language="javascript">
var form = document.getElementById('ic');
alert(form.getAttribute('id'));
</script>
</body>
</html>
If an image on a form has an id that has as id content the text "id", then
something strange happens in IE.
You get an [object] instead of the actual id content. This can happen when
the wicket automatic id generation is used.
Could there be a workaround included within wicket to avoid this bug?
(We have spent quite some time to debug this issue, so if wicket can include
a workaround, it can save others the same debugging work)
Thank you very much for any reaction.
--
View this message in context:
http://www.nabble.com/IE-bug-causes-wicket-problems-when-id-auto-generation-is-active-tp17231936p17231936.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
