Updates:
        Status: Available
        Owner: [EMAIL PROTECTED]
        Cc: [EMAIL PROTECTED]
        Labels: Mstone-1.1 NewHTTP

Comment #8 on issue 1085 by [EMAIL PROTECTED]: Several AJAX-defects when  
using Chrome with the Wicket-Framework
http://code.google.com/p/chromium/issues/detail?id=1085

In another thread Joel said, "It appears that the problem is intermittent.  
I have
tried the examples numerous times, and on occasion they work, and on   
others they do
not. I'm not sure what might be causing the issue, but since I last spoke  
to you it
stopped working, when I restarted Chrome it started working again.

"Needless to say I always ensure that the same page is working in other
browsers (ff & ie) at the same time, which it is.

"The page I am testing this against is:
http://www.wicketstuff.org/wicket13/ajax/lazy-loading.11

"I've attached an image with the js debug error ("ERROR: Error while
parsing response: Could not find root <ajax-response> element")"

I am going to re-open this while the lazy-loading sample continues to fail
intermittently.  Perhaps this is an issue with the network stack or  
Javascript?  How
do we respond to a network being flakey?

Joel, have you tried this with the nightly builds from
http://build.chromium.org/buildbot/continuous/LATEST/ also, what does your  
network
look like?  Are you going over wireless, through a proxy, etc?


-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-bugs" group.
To post to this group, send email to chromium-bugs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to