kazu2012 / persevere-framework

Automatically exported from code.google.com/p/persevere-framework
0 stars 0 forks source link

Customers example - comet updates not working in Firefox #195

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. launch the Customers example from the local examples page (via persevere
server)... do this in both IE and FF
2. in IE, make a change to the data and click save
3. notice the data does not update in FF
4. reverse the process (update data in FF and save) - notice it updates
fine in IE

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
beta3 binaries from project page on google code

Please provide any additional information below.

Original issue reported on code.google.com by ryan.g...@gmail.com on 3 Jun 2009 at 5:48

GoogleCodeExporter commented 8 years ago
Sorry for the bug format... it's pretty self explanatory in steps 1-4 though.

Original comment by ryan.g...@gmail.com on 3 Jun 2009 at 5:48

GoogleCodeExporter commented 8 years ago
I can't seem to reproduce this with these steps. Do you have any more 
information on 
how to reproduce this? How did you start Persevere? Any JavaScript errors or 
server 
errors?

Original comment by kris...@gmail.com on 4 Jun 2009 at 5:39

GoogleCodeExporter commented 8 years ago
I can actually reproduce this at http://www.persvr.org/examples/customer.html

I'm using FF version 3.0.10

There are no errors in firebug, but the request to /channels never stops 
spinning
(though I guess I'd expect that). I tried turning firebug off as well to see if
that's messing it up, and same results (the data doesn't auto update for me in 
FF).

Original comment by ryan.g...@gmail.com on 4 Jun 2009 at 5:58

GoogleCodeExporter commented 8 years ago
I did see a similar issue to this a while back when I had Persevere running 
behind Apache.  I took Apache out 
going straight to Jetty and this cured the problem.  Something about passing 
Channels through my Apache 
configuration didn't work, but I'm not familiar enough with Apache to fix it so 
I changed my setup.

Original comment by pvolkaer...@gmail.com on 6 Jun 2009 at 9:05