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

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

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

Igor Vaynberg resolved WICKET-1817.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Igor Vaynberg

we are not going to put time and effort into what may very well turn out to be bugs in chrome. i mean come on, do you really expect us to support a 0.2 version of a browser???

> 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
>            Assignee: Igor Vaynberg
>            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.