[jira] Updated: (WICKET-1817) Many of the standard ajax components fail to work in Google Chrome

["Martijn Dashorst (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Dashorst updated WICKET-1817:
-------------------------------------

    Priority: Minor  (was: Critical)

1. This is NOT critical!!!!!!
2. This may not be a bug in Wicket, did you ever consider that the new JS implementation of Google is broken?
3. This is NOT critical!!!!
4. Google Chrome is an alpha product
5. Google Chrome is an alpha product
6. Google Chrome is an alpha product
7. See 1



> Many of the standard ajax components fail to work in Google Chrome
> ------------------------------------------------------------------
>
>                 Key: WICKET-1817
>                 URL: https://issues.apache.org/jira/browse/WICKET-1817
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket, wicket-extensions
>    Affects Versions: 1.3.4, 1.4-M3
>         Environment: Google Chrome, Windows XP
>            Reporter: Ilya Boyandin
>            Priority: Minor
>
> All these wicket ajax examples don't work in Chrome: tree, treetable, modal, editable label, clock, effects, guestbook, lazy loading, links, on change ajax updater, pageable, ratings, tabbed panel, todo list.
> The debug output looks like this in all of them:
> INFO: Using XMLHttpRequest transport
> INFO:
> INFO: Initiating Ajax GET request on ?wicket:interface=:3:treeTable:i:10:sideColumns:0:nodeLink::IBehaviorListener:0:&random=0.9150353251025081
> INFO: Invoking pre-call handler(s)...
> INFO: Received ajax response (0 characters)
> INFO: 
> ERROR: Error while parsing response: Could not find root <ajax-response> element
> INFO: Invoking post-call handler(s)...
> INFO: Invoking failure handler(s)...

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