[Tickets #10835] Re: Spooky behavior after midnight

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10835
------------------------------------------------------------------------------
  Ticket             | 10835
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Spooky behavior after midnight
  Queue              | IMP
  Version            | Git master
  Type               | Bug
-State              | Feedback
+State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-12-14 01:04) wrote:

Finally could reproduce.  The problem was that on a metadata reset  
(e.g. a day change), we were not converting the thread object into a  
Hash object on the initial reset.  Thus, the behavior was only  
manifesting itself when the mailbox changed after the metadata reset  
(e.g. deleting a message; new message in mailbox).  This was causing a  
JS error that caused ViewPort.isbusy to remain true indefinitely,  
causing any future ajaxResponse() calls to fail.

Very weird that no JS error appeared for you.