[dev] git - DIMP: Reply/Forward popups currently non functional

[Rick Romero]

Quoting Ronan SALMON <rsalmon at mbpgroup.com>:

> Rick Romero <rick at havokmon.com> a écrit :
>>> FYI.
>>>
>>> In DIMP, if you highlight a message and click 'Reply' or 'Forward' -
>>> a window will pop up ( also FYI - despite the Compose in New Window
>>> preference unchecked) that just says 'Loading..'
>>> Viewing the Source shows all the data appears to exist, but the JS
>>> 'show()' doesn't seem to be executed after page load.   This also
>>> occurs for "New" Message.  Which all seem to be tied to
>>> compose-dimp.js.
>>>
>>> Note - This DOES NOT occur if you double click a message to open it
>>> in a new window - it will appear correctly, and both Reply and
>>> Forward within the new window are working.   This one appears to be
>>> message-dimp.js
>
> Hi,
>
> I am seeing this as well. This started to appear about 3-4 weeks  
> ago. But I still haven't figured out why this is happening. There  
> aren't any errors/warnings (horde.log, apache, firebug).
>
> If I change imp/templates/dimp/compose/compose-base.html as mention  
> below, I can see the div "Loading", but everything works just fine  
> and still no error.
> - <div id="pageContainer" style="display:none">
> + <div id="pageContainer">
>
> I tried with the default (horde/imp) pref values.
> I use FF 3.6.12.
>
> Any hit on how I can debug this?

I did try manually tracing the Javascript - the only noticable  
difference was that opening a message included dimpcore.js and  
dimpbase.js, and simply replying included dimpbase.js.  Inlcuding the  
missing .js did not have any affect.  AFAICT, there are no Javascript  
errors, and everything appears to be in order.  It just seems that  
message-dimp.js executes $('pageContainer').show();, while  
compose-dimp.js does not... \o/

I've removed imp and re-checked it out, cleared local cache, proxy  
cache, and cleared memcache, restarted lighttpd (sometimes lighttpd  
doesn't pick up changes) - and I still have the issue.  I figured it  
was something else in my setup.

Rick