Ajax responses do not update DOM correctly on Opera
---------------------------------------------------

                 Key: WICKET-2851
                 URL: https://issues.apache.org/jira/browse/WICKET-2851
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.4.7
         Environment: This issue affects just Opera, my tested version is 10.52.

Other browsers I tested but are not affected by the issue: Firefox 3.6.3, IE 
8.0, Chrome 4.1.249.1059.
Application was deployed on Apache Tomcat 5.5.28 and Jetty 6.1.6.
Everything runs on MS Win 7 Ultimate x64.
            Reporter: Martin Petras


Having following example:

========= HTML ==========
<table>
        <tr><td><button wicket:id="btnShowHide">Show/Hide</button></td></tr>
        <tr wicket:id="hidingContainer"><td>something goes here...</td></tr>
</table>

========= PAGE ==========
final Component hidingContainer;
this.add(hidingContainer = new 
WebMarkupContainer("hidingContainer").setOutputMarkupId(
                true).setOutputMarkupPlaceholderTag(true).setVisible(true));
                                
this.add(new AjaxFallbackLink<Void>("btnShowHide"){

        @Override
        public void onClick(AjaxRequestTarget target) {
                hidingContainer.setVisible(!hidingContainer.isVisible());
                target.addComponent(hidingContainer);
        }
});


On Opera browser it works well only once. Afterwards it is not possible to 
show/hide hidingContainer.

Ajax response doesn't update hidingContainer's DOM properly. Response is 
correct, however after replacing existing html code with an incomming html the 
TR tag looses its ID attribute. Hence the following Ajax response fails to 
update the TR tag and throws error:
ERROR: Wicket.Ajax.Call.processComponent: Component with id 
[[hidingContainer4]] a was not found while trying to perform markup update. 

This problem occurs only when hidingContainer is in a TR tag. If replaced with 
<p>, everything works like a charm.

It must be a bug in the Opera browser but maybe there is any workaround that 
may get it work.

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

Reply via email to