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

[jira] Closed: (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:all-tabpanel ]

marques closed WICKET-1068.
---------------------------

    Resolution: Won't Fix

Ok so I have verified that this is an issue only for beta3. I just tested on beta4 and it works as expected.

> 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
>            Assignee: Matej Knopp
>             Fix For: 1.3.0-beta5
>
>         Attachments: SafariAjaxBug.zip
>
>
> 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.