[jira] Commented: (WICKET-1087) Ajax update on a panel caused markup outside the panel to be missing

["Matej Knopp (JIRA)" <ji...@apache.org>]

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

Matej Knopp commented on WICKET-1087:
-------------------------------------

I'm affraid there is nothing we can do. The issue is caused by firefox being "too smart" when parsing the html. It considers the <div /> to be a <div> and treats the rest as if you forgot to close the div tag. I don't think it's right thing to do, especially not in standard compliance mode. But it does it nonetheless.

So the result is that firefox thinks that <div>footer</div> is part for the <div id="container6">, because it considers the <div /> to be an opening tag. 

There is one think we could do about this though. Maybe during markup parsing we could replace all <div /> tags with <div></div>

> Ajax update on a panel caused markup outside the panel to be missing
> --------------------------------------------------------------------
>
>                 Key: WICKET-1087
>                 URL: https://issues.apache.org/jira/browse/WICKET-1087
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta4
>         Environment: Tested with Firefox 2.0.0.7, other browsers unknown
>            Reporter: kent lai
>            Assignee: Matej Knopp
>            Priority: Minor
>             Fix For: 1.3.0-beta5
>
>         Attachments: WicketTest.zip
>
>
> I was doing an ajax content update with Wicket, replacing the entire content of a panel with another panel (different markup files).
> After receiving the response, the content after the updated panel disappears.
> I checked that the ajax response is correct from the Wicket Ajax Debug panel, but the Wicket client side javascript seemed to have removed all the DOM elements from the updated panel onwards.
> I have replicated the issue and attached as a sample project.
> The issue seemed to be caused from a <div /> tag within the first panel. Changing it from <div></div> seemed to be a work around for now, but I am unsure if there might be similar issues with other tags (imagine having to change <br /> to <br></br> and other similar tags!)

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