Tickets :: [#6590] Blank page when selecting alternative calendar

6.0.0-alpha10

5/14/25

Summary	Blank page when selecting alternative calendar
Queue	Horde Base
Queue Version	HEAD
Type	Bug
State	Stalled
Priority	1. Low
Owners
Requester	jochem (at) mondrian (dot) nl
Created	04/10/2008 (6243 days ago)
Due
Updated	04/27/2016 (3304 days ago)
Assigned	01/29/2009 (5949 days ago)
Resolved	09/17/2009 (5718 days ago)
Milestone
Patch	No

09/17/2009 05:31:32 PM	patrickdk (at) patrickdk (dot) com	Comment #22	Reply to this comment
From ~~bug 8580~~. I tried this patch, and it fixes the problem on all my test machines.

09/17/2009 05:20:24 PM	CVS Commit	Comment #21	Reply to this comment
Changes have been made in CVS for this ticket: ~~Bug: 6590~~ MFB http://cvs.horde.org/diff.php/horde/docs/CHANGES?rt=horde&r1=1.1260&r2=1.1261&ty=u http://cvs.horde.org/diff.php/horde/js/prototype.js?rt=horde&r1=1.19&r2=1.20&ty=u

09/17/2009 05:15:54 PM	Michael Slusarz	Comment #20 State ⇒ Stalled	Reply to this comment
Michael bangs head against the wall multiple times. Due to me misreading this page: https://prototype.lighthouseapp.com/projects/8886/tickets/90-cloneposition-problem-in-ie7 this wasn't fixed in 1.6.1 either. Although I can't reproduce on my installations, the core problem should remain because that prototypejs bug has not yet been closed. So we need to repatch again. This is my fault again (although, in my defense, I specifically tested this when updating to 1.6.1 and it worked fine for me).

09/17/2009 05:15:32 PM	CVS Commit	Comment #19	Reply to this comment
Changes have been made in CVS for this ticket: ~~Bug: 6590~~ Unbelievable. http://cvs.horde.org/diff.php/chora/js/prototype.js?rt=horde&r1=1.14.2.3&r2=1.14.2.4&ty=u http://cvs.horde.org/diff.php/chora/js/src/prototype.js?rt=horde&r1=1.12.2.3&r2=1.12.2.4&ty=u http://cvs.horde.org/diff.php/gollem/js/prototype.js?rt=horde&r1=1.12.2.3&r2=1.12.2.4&ty=u http://cvs.horde.org/diff.php/gollem/js/src/prototype.js?rt=horde&r1=1.10.2.3&r2=1.10.2.4&ty=u http://cvs.horde.org/diff.php/horde/docs/CHANGES?rt=horde&r1=1.515.2.561&r2=1.515.2.562&ty=u http://cvs.horde.org/diff.php/horde/js/prototype.js?rt=horde&r1=1.11.2.8&r2=1.11.2.9&ty=u http://cvs.horde.org/diff.php/horde/js/src/Attic/prototype.js?rt=horde&r1=1.7.2.6&r2=1.7.2.7&ty=u http://cvs.horde.org/diff.php/imp/js/Attic/prototype.js?rt=horde&r1=1.21.2.9&r2=1.21.2.10&ty=u http://cvs.horde.org/diff.php/imp/js/src/Attic/prototype.js?rt=horde&r1=1.13.2.6&r2=1.13.2.7&ty=u http://cvs.horde.org/diff.php/ingo/js/Attic/prototype.js?rt=horde&r1=1.4.2.7&r2=1.4.2.8&ty=u http://cvs.horde.org/diff.php/ingo/js/src/Attic/prototype.js?rt=horde&r1=1.4.2.6&r2=1.4.2.7&ty=u http://cvs.horde.org/diff.php/kronolith/js/Attic/prototype.js?rt=horde&r1=1.14.2.9&r2=1.14.2.10&ty=u http://cvs.horde.org/diff.php/kronolith/js/src/Attic/prototype.js?rt=horde&r1=1.10.2.6&r2=1.10.2.7&ty=u http://cvs.horde.org/diff.php/mnemo/js/Attic/prototype.js?rt=horde&r1=1.3.2.8&r2=1.3.2.9&ty=u http://cvs.horde.org/diff.php/mnemo/js/src/Attic/prototype.js?rt=horde&r1=1.6.2.6&r2=1.6.2.7&ty=u http://cvs.horde.org/diff.php/nag/js/Attic/prototype.js?rt=horde&r1=1.4.2.9&r2=1.4.2.10&ty=u http://cvs.horde.org/diff.php/nag/js/src/Attic/prototype.js?rt=horde&r1=1.8.2.6&r2=1.8.2.7&ty=u http://cvs.horde.org/diff.php/turba/js/Attic/prototype.js?rt=horde&r1=1.12.2.8&r2=1.12.2.9&ty=u http://cvs.horde.org/diff.php/turba/js/src/Attic/prototype.js?rt=horde&r1=1.9.2.6&r2=1.9.2.7&ty=u

09/16/2009 04:47:24 PM	Michael Slusarz	Comment #18 State ⇒ Resolved	Reply to this comment
This was fixed with an upgrade to prototypejs v1.6.1.

01/29/2009 03:45:48 PM	Chuck Hagenbuch	Comment #17 State ⇒ Stalled Priority ⇒ 1. Low	Reply to this comment
Stalling with the other bugs waiting for an official prototype patch.

01/29/2009 12:02:11 PM	Jan Schneider	Comment #16 State ⇒ Feedback	Reply to this comment
Why is this still assigned? Isn't the problem fixed now after we patched prototype again?

12/10/2008 06:05:34 PM	Michael Slusarz	Comment #15 Queue ⇒ Horde Base Priority ⇒ 3. High State ⇒ Assigned Version ⇒ HEAD	Reply to this comment
sigh This bug was not fixed in prototype 1.6.0.3 despite some literature stating otherwise. The previous patch has thus been applied to prototypejs v1.6.0.3.

12/10/2008 06:04:35 PM	CVS Commit	Comment #14	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/chora/js/prototype.js?r1=1.14.2.1&r2=1.14.2.2&ty=u http://cvs.horde.org/diff.php/chora/js/src/prototype.js?r1=1.12.2.1&r2=1.12.2.2&ty=u http://cvs.horde.org/diff.php/gollem/js/prototype.js?r1=1.12.2.1&r2=1.12.2.2&ty=u http://cvs.horde.org/diff.php/gollem/js/src/prototype.js?r1=1.10.2.1&r2=1.10.2.2&ty=u http://cvs.horde.org/diff.php/horde/js/prototype.js?r1=1.11.2.6&r2=1.11.2.7&ty=u http://cvs.horde.org/diff.php/horde/js/src/prototype.js?r1=1.7.2.4&r2=1.7.2.5&ty=u http://cvs.horde.org/diff.php/imp/js/Attic/prototype.js?r1=1.21.2.7&r2=1.21.2.8&ty=u http://cvs.horde.org/diff.php/imp/js/src/Attic/prototype.js?r1=1.13.2.4&r2=1.13.2.5&ty=u http://cvs.horde.org/diff.php/ingo/js/Attic/prototype.js?r1=1.4.2.5&r2=1.4.2.6&ty=u http://cvs.horde.org/diff.php/ingo/js/src/Attic/prototype.js?r1=1.4.2.4&r2=1.4.2.5&ty=u http://cvs.horde.org/diff.php/kronolith/js/Attic/prototype.js?r1=1.14.2.6&r2=1.14.2.7&ty=u http://cvs.horde.org/diff.php/kronolith/js/src/Attic/prototype.js?r1=1.10.2.4&r2=1.10.2.5&ty=u http://cvs.horde.org/diff.php/mnemo/js/Attic/prototype.js?r1=1.3.2.6&r2=1.3.2.7&ty=u http://cvs.horde.org/diff.php/mnemo/js/src/Attic/prototype.js?r1=1.6.2.4&r2=1.6.2.5&ty=u http://cvs.horde.org/diff.php/nag/js/Attic/prototype.js?r1=1.4.2.7&r2=1.4.2.8&ty=u http://cvs.horde.org/diff.php/nag/js/src/Attic/prototype.js?r1=1.8.2.4&r2=1.8.2.5&ty=u http://cvs.horde.org/diff.php/turba/js/Attic/prototype.js?r1=1.12.2.6&r2=1.12.2.7&ty=u http://cvs.horde.org/diff.php/turba/js/src/Attic/prototype.js?r1=1.9.2.4&r2=1.9.2.5&ty=u

12/10/2008 06:01:04 PM	CVS Commit	Comment #13	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/chora/js/prototype.js?r1=1.14&r2=1.15&ty=u http://cvs.horde.org/diff.php/chora/js/src/prototype.js?r1=1.12&r2=1.13&ty=u http://cvs.horde.org/diff.php/gollem/js/prototype.js?r1=1.12&r2=1.13&ty=u http://cvs.horde.org/diff.php/gollem/js/src/prototype.js?r1=1.10&r2=1.11&ty=u http://cvs.horde.org/diff.php/horde/js/prototype.js?r1=1.15&r2=1.16&ty=u http://cvs.horde.org/diff.php/horde/js/src/prototype.js?r1=1.12&r2=1.13&ty=u http://cvs.horde.org/diff.php/hordeweb/js/prototype.js?r1=1.9&r2=1.10&ty=u http://cvs.horde.org/diff.php/hordeweb/js/src/prototype.js?r1=1.8&r2=1.9&ty=u

05/18/2008 10:23:18 AM	Jan Schneider	State ⇒ Stalled

05/05/2008 07:33:14 PM	Michael Slusarz	Comment #12 Priority ⇒ 1. Low State ⇒	Reply to this comment
Reopen - since at some point (hopefully) we won't need this patch anymore.

05/02/2008 09:18:45 PM	Chuck Hagenbuch	Comment #11 State ⇒ Resolved	Reply to this comment
Patch for the prototype bug has been applied to our CVS.

04/18/2008 05:54:29 PM	john (dot) david (dot) dalton (at) gmail (dot) com	Comment #10	Reply to this comment
Hello Michael , It looks like you are using an older version of YUI compressor, newer versions work with Prototype 1.6 and its use of the $super variable. You may also use a modified dean edwards packer found in ProtoSafe, or you can use the precompressed version in ProtoPack: http://code.google.com/p/protosafe/downloads/list The erroneous compression is whats causing the ajax-y related bugs because the ajax methods use the $super variable which was changed to something like "C" when you compressed it in the older verson of YUI compressor. The element style error is related to that ticket: http://dev.rubyonrails.org/ticket/11473#comment:19

04/18/2008 04:43:12 AM	Michael Slusarz	Comment #9	Reply to this comment
Can anyone confirm that the prototype bugfix fixes this? Verified that the prototype patch fixes this (and ~~ticket 6602~~).

04/11/2008 06:49:05 PM	Chuck Hagenbuch	Comment #8	Reply to this comment
Can anyone confirm that the prototype bugfix fixes this?

04/11/2008 04:20:05 PM	Michael Slusarz	Comment #7	Reply to this comment
Almost 100% sure this is a prototypejs bug. See: http://dev.rubyonrails.org/ticket/11007 http://dev.rubyonrails.org/ticket/11473 Looks like it is fixed in 1.6.0.3 (which is not yet released).

04/11/2008 03:32:53 PM	jochem (at) mondrian (dot) nl	Comment #6	Reply to this comment
I can confirm that this also happens on IE6, and was happening before this IE7 started giving similar issues.

04/11/2008 03:20:27 PM	Michael Rubinsky	Comment #5	Reply to this comment
FWIW, this sounds like the exact same issue I was having (in IE 6 only though) that lead me to re-compress prototype.js (http://lists.horde.org/archives/cvs/Week-of-Mon-20080218/075089.html). I'm seeing it again now in IE 6 and IE 7 although in IE 7 it's only when doing "ajax-y" thinks like the original post below. in IE 6 it happens during ajax-y things as well as when navigating from one time span to another..both with the "style is not an object error." Using the uncompressed version of prototype still yields the error - it's line 2253 of prototype.js

04/11/2008 12:40:41 PM	jochem (at) mondrian (dot) nl	Comment #4	Reply to this comment
I just updated horde with cvs update -PdC in the horde/ directory (confirmed that kronolith also got updated), I've done that again this morning before testing with the src scripts and yet again cleared cache, and I still see the same behavior. This is the error I get now: Line: 2253 Char: 5 Error: 'style' is null or not an object' code: 0 URL: https://domain.tld/horde/kronolith/

04/10/2008 03:27:42 PM	Chuck Hagenbuch	Comment #3 State ⇒ Feedback	Reply to this comment
Are you using latest CVS of both Horde and Kronolith, and have you cleared your browser caches? I think I fixed something similar to this a few weeks ago or more. If not, you can use the .js files in js/src/ (just copy them over the js/ files) to get a better line number and error message.

04/10/2008 10:59:04 AM	jochem (at) mondrian (dot) nl	Comment #2	Reply to this comment
This also occurs when trying to go to the next or previous month, so I'm assuming it's any AJAX-y action that's causing this problem. A colleague of mine just reported that she's had this problem all week, while I just updated to the latest version of horde this morning (the previous update round being a couple of months ago), so I also assume this is a bug introduced by a Microsoft update. If a fix to this problem is going to take a while, is there a way to turn off the AJAX in kronolith?

04/10/2008 10:17:56 AM	jochem (at) mondrian (dot) nl	Comment #1 State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ Kronolith Summary ⇒ Blank page when selecting alternative calendar Type ⇒ Bug Priority ⇒ 3. High	Reply to this comment
When I try to check a second calendar (or uncheck the first one) in the little side box in kronolith, while using IE7, I get a completely white screen (the right frame when having the sidebar enabled), with an "error on page": Line 2 Char 38133 Error 'style' is null or not an object I think I've tracked it down to kronolith/js/prototype.js, but as this file is apparently run through a mangler / optimizer, I can't fix it myself. Seamonkey and Firefox seem to have no problems.