[Tickets #8267] Re: DIMP preview errors in folders other than Inbox

bugs at horde.org bugs at horde.org
Sun May 31 03:48:04 UTC 2009


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

Ticket URL: http://bugs.horde.org/ticket/8267
------------------------------------------------------------------------------
  Ticket             | 8267
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | DIMP preview errors in folders other than Inbox
  Queue              | DIMP
  Version            | 1.1.2
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-05-30 23:48) wrote:

>>> Also, the older Firefox's don't do it. I tried 3.0.8, 3.0.9, and
>>> 3.0.10 on some different PCs and 3.0.5 on the same PC as 3.5 runs on,
>>> and none of them do it. FF3.5 and Chrome both do have the problem.
>>
>> DIMP 1.1.2 doesn't support FF 3.5.  This is almost certainly a
>> prototypejs issue since that is the js library responsible for all
>> the fancy attribute matching.
>
> On further testing, DIMP 1.1.x works just fine on FF 3.5b4 (Windows
> 7) and Chrome (WinXP).
>
> Further analysis of the error message provided (Expected
> identifier...) indicates this is an internal issue with firebug (it
> is thrown by the xulrunner stuff) rather than anything that
> should/would be affecting DIMP.
>
> The unfortunate reality is, without a reliable way to reproduce
> and/or patch, this bug will need to be closed especially since I can
> not reproduce on anything resembling a stable browser (I do not yet
> consider Chrome stable).

Verified on Chrome 2 (not Chrome 1).  Either Chrome 2 or prototypejs  
is broken - this is the line that isn't working properly (in  
_addMouseEvents in DimpBase.js):

elt = $(p.id).down('div.msCheck')

It is the selector 'div.msCheck' that is broken on Chrome - it returns  
an undefined value instead of a DOM element (a DIV element of class  
'msCheck' does exist).

Simply put, this is not a Horde/IMP/DIMP issue.






More information about the bugs mailing list