[ http://issues.apache.org/jira/browse/BEEHIVE-317?page=history ]
Daryl Olander resolved BEEHIVE-317:
-----------------------------------
Assign To: Alejandro Ramirez (was: Daryl Olander)
Resolution: Fixed
The problem here was that IE was caching the XmlHttpRequest results and feeding
them back instead of hitting the server. This meant that the tree state on the
server was not updated, but on the client everything appeared to run normally.
I fixed this by putthing the no-cache stuff into the response to prevent IE
from caching the results.
> Failing to update the collapse state in IE 6.0
> ----------------------------------------------
>
> Key: BEEHIVE-317
> URL: http://issues.apache.org/jira/browse/BEEHIVE-317
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Environment: IE 6.0
> Reporter: Daryl Olander
> Assignee: Alejandro Ramirez
> Priority: Critical
> Fix For: V1Beta
>
> Just found a bad IE bug in the tree. Inside a runAtClient tree do the
> following:
> 1) Create a tree with all nodes expanded (coreWeb/tree/images)
> 2) Contract any node
> 3) Expand that same node
> 4) Contract it again
> 5) Hit select on another node...
> What happens at this point is that the not that should be contracted with be
> expanded.
> This works in both Firefox and Opera (This requires the fix for bug 255 which
> is in the works.)
> What is happening is that the XmlHttpRequest to collapse the tree doesn't
> happen the second time. The JavaScript collapsing the tree does run, but for
> some reason the requset is not getting to the server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
