[Tickets #3527] NEW: Calendar navigation buttons break sidebar horde_main frame target (IE only)

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3527
-----------------------------------------------------------------------
 Ticket             | 3527
 Created By         | tevans at tachometry.com
 Summary            | Calendar navigation buttons break sidebar horde_main frame target (IE only)
 Queue              | Kronolith
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


tevans at tachometry.com (2006-02-23 17:00) wrote:

Versions:
---------------
Kronolith: CVS HEAD as of 2/20/2006
Framework: CVS HEAD as of 2/20/2006
Server: LAMP (FC2, Apache 2.0.58, MySQL 3.23.58; PHP 4.3.10)
Client: Windows XP
Browser: IE 6.0.2900.2180 (does not affect Mozilla)
Tested using multiple skins: bluewhite, mozilla, simplex

Summary:
--------------
After using either of the previous/next navigation arrow buttons in the week
or month calendar view, all links in the sidebar cause IE to open a new
browser window rather than writing the content of the target page into the
horde_main frame as expected.  

Links in the sidebar are restored to normal operation only after logging
out.

Procedure to recreate bug:
-------------------------------------
1) Login to Horde using MS Internet Explorer
2) Select "Calendar" from sidebar
3) Click either "Last" or "Next" navigation arrow in week or month view
4) Select any item from the sidebar

Result: 
----------
All sidebar links now open in a new browser window rather than resusing the
horde_main frame. The user must log out and log back in to restore normal
sidebar operation.

Workarounds:
---------------------
We have suggested to our IE users to either switch to a Mozilla/Firefox
browser or to use the "Goto" calendar button instead of the navigation
arrows.

Analysis:
-------------
We have done some cursory review of the HTML templates, JS, and CSS looking
for clues, but have come up with nothing obvious that would cause (or
correct) this behavior. 

Has anyone else seen this kind of framing issue?