[
https://issues.apache.org/jira/browse/WICKET-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526408
]
Rüdiger Schulz commented on WICKET-938:
---------------------------------------
I also had a problem with Konqueror / Safari and Ajax updates in beta 3, and I
can confirm it works now with the current snapshot.
(see http://www.nabble.com/Ajax-error-in-Safari---Konqueror-tf4415279.html)
> Second and subsequent ajax component updates fail in Safari
> -----------------------------------------------------------
>
> Key: WICKET-938
> URL: https://issues.apache.org/jira/browse/WICKET-938
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta3
> Environment: Mac OS 10.4.10, Safari 2.0.4
> Reporter: Nathan Hamblen
> Assignee: Matej Knopp
> Fix For: 1.3.0-beta4
>
>
> Ajax updates in Safari will work the first time, but not on subsequent ajax
> requests (nothing happens). The same pages work fine in Firefox, or in Safari
> if I revert to beta2. The Safari javascript console doesn't show any error,
> but the Wicket ajax debug window has messages like this one:
> ERROR: Component with id [[feedback15]] a was not found while trying to
> perform markup update. Make sure you called component.setOutputMarkupId(true)
> on the component whose markup you are trying to update.
> Outputting the markup id isn't the problem, since it works for the first
> request. It seems that the markup id has fallen out of sync between the
> browser and the server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
