FYI, I just checked Chrome and it works fine too. The problem appears isolated to Firefox.
On 05/17/2013 05:38 PM, Ján Máté wrote:
I really don't know ... if the next RC will not fix your problem, then we can check your setup (but there are TON of fixes since the last RC, so I hope it will work).
JM
On May 17, 2013, at 11:34 PM, Ken Murchison murch@andrew.cmu.edu wrote:
Thanks. I look forward to the fix.
Just curious, why does Safari work? Does it have something to do with the format of my sync report or multiget report response and WebKit does a better job of parsing it?
On 05/17/2013 05:28 PM, Ján Máté wrote:
Hi Ken,
0.8.1.1 is complatible ONLY with DAViCal. This problem is fixed (I hope) in our GIT /fixed yesterday by using a demo Baikal server/ ... just wait few days for the next release candidate (we are still working on one additional fix).
JM
On May 17, 2013, at 11:11 PM, Ken Murchison murch@andrew.cmu.edu wrote:
I have version 0.8.1.1 running against the server that I am developing and it works perfectly with Safari 6.0.4. However with Firefox (v20.1 on Fedora 18 and v21.0 on WinXP) when the client starts up it does not display any existing events in the calendars. It allows me to create new events and will display them until I log out. When I log back in, any events that I created no longer display. They do show up in CalDAVZap/Safari, iCal, and Lightning.
Is there a config option that I need to flip in Firefox to fix this?
-- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University
-- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University
On Fri, 17 May 2013 17:42:35 -0400 Ken Murchison murch@andrew.cmu.edu wrote:
FYI, I just checked Chrome and it works fine too. The problem appears isolated to Firefox.
Well, at my end its the apposite. Firefox 21.0 works but the tab running caldavzap in chrome 26.0.1410.43 crashes when it is coming to the point where the calendar data is supposed to be rendered.
There are MAJOR bugs in Chrome regex engine - substring matching (used for event parsing) can take Nx10 seconds in some cases (and sometime it also crashes).
See: http://code.google.com/p/chromium/issues/detail?id=146162 http://code.google.com/p/chromium/issues/detail?id=123449
So if you have a Chrome *UNFRIENDLY* event/todo/contact it can really crash - I simplified some regexes, so maybe the new version will "work" for you.
JM
On May 17, 2013, at 11:51 PM, Michael Rasmussen mir@datanom.net wrote:
On Fri, 17 May 2013 17:42:35 -0400 Ken Murchison murch@andrew.cmu.edu wrote:
FYI, I just checked Chrome and it works fine too. The problem appears isolated to Firefox.
Well, at my end its the apposite. Firefox 21.0 works but the tab running caldavzap in chrome 26.0.1410.43 crashes when it is coming to the point where the calendar data is supposed to be rendered.
-- Hilsen/Regards Michael Rasmussen
Get my public GnuPG keys: michael <at> rasmussen <dot> cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir <at> datanom <dot> net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir <at> miras <dot> org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
"Probably the best operating system in the world is the [operating system] made for the PDP-11 by Bell Laboratories." - Ted Nelson, October 1977
On Sat, 18 May 2013 00:33:31 +0200 Ján Máté jan.mate@inf-it.com wrote:
So if you have a Chrome *UNFRIENDLY* event/todo/contact it can really crash - I simplified some regexes, so maybe the new version will "work" for you.
Its no big deal. As long as you are aware of the bug in Chrome and alternatives are available then it's fine with me. FF suits me fine;-)