You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Matej Knopp (JIRA)" <ji...@apache.org> on 2007/10/13 16:09:50 UTC

[jira] Commented: (WICKET-1068) Wicket.replaceOuterHtml is broken in Safari 2.x (1.3.0-beta3)

    [ https://issues.apache.org/jira/browse/WICKET-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534539 ] 

Matej Knopp commented on WICKET-1068:
-------------------------------------

If you want this to get resolved you need to provide a quickstart, because I'm not able to reproduce it. Also can you test it with latest trunk (or at least beta 4) to see if it's not fixed already?

> Wicket.replaceOuterHtml is broken in Safari 2.x (1.3.0-beta3)
> -------------------------------------------------------------
>
>                 Key: WICKET-1068
>                 URL: https://issues.apache.org/jira/browse/WICKET-1068
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>         Environment: MacOSX 10.4.8, Safari 2.0.4
>            Reporter: marques
>             Fix For: 1.3.0-beta5
>
>
> in wicket-ajax.js, new implementation of Wicket.replaceOuterHtml is broken in Safari 2.x  -- this is due to a bug in Safari where creating a dom element with an id attribute containing the same value as an existing element renders one of them un-gettable via document.getElementById. A possible solution is to set the original element's id to undefined before creating the replacement element, or to use Safari's native outerHTML feature (as in beta2, but selecting for safari only as to avoid problems with other browser's implementations of outerHTML)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.