Bug 449353 - New meetings gain data from previously viewed meetings in Zimbra
Summary: New meetings gain data from previously viewed meetings in Zimbra
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: firefox
Version: 5.1
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Gecko Maintainer
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-02 11:29 UTC by Richard Monk
Modified: 2008-06-09 21:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-09 21:57:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Richard Monk 2008-06-02 11:29:57 UTC
Description of problem:

If you open up a new meeting after having opened other meetings using Firefox
1.5, there is a chance that the attendees list or other info from the previous
meeting will appear in the window.  This can cause meetings to be created with
the wrong attendee list or other anomalies.

Version-Release number of selected component (if applicable):
Firefox 1.5.0.12-11
Zimbra 5.0.4

How reproducible:

Steps to Reproduce:
1. View meetings in zimbra web interface (advanced mode)
2. Open/edit a meeting
  
Actual results:
Meeting occasionally contains details of other meetings (attendee list)

Expected results:
Meeting contains blank info (for new meeting) or existing data (for edit).  If
you save the meeting, the "bad" data gets written into the meeting.

Additional info:  This is most likely a bug in the Zimbra 5 javascript, as I
have not had any reports of this effect under Firefox 2 or 3, any version.

Comment 1 Matěj Cepl 2008-06-02 20:09:18 UTC
Could you reproduce this with upcoming FF3 in RHEL 5.2, please?

Comment 2 Richard Monk 2008-06-03 11:29:48 UTC
I have been unable to duplicate this in Firefox 3.

Comment 3 Matěj Cepl 2008-06-09 21:57:00 UTC
Closing as NEXTRELEASE. Reopen, if you are able to reproduce this with the
current version of Firefox.


Note You need to log in before you can comment on or make changes to this bug.