[imp] undefined JS function after resize

[Oliver Schulze L.]

The resize issue in Netscape is a know issue, but the javascript I 
haven't hear of.
Try the latest Netscape build 4.77.

Another thing you can do is to have a link from your site to yout IMP 
instalation.
This link will open a Netscape window with the resize option off, maybe 
the same
size of the screen. This will prevent users from resizing when visiting 
you IMP instalation.
You can do it all with javacript.

Good luck
Oliver

Alexander Dietz wrote:

>[Subject was: Javascript "function" syntax]
>
>OK, it was a really stupid thing to think, that changing those function
>definitons by deleting a space would change anything...
>
>I discovered the following now (configuration: horde 1.2.4 / imp 2.2.4 /
>Server Version: Apache/1.3.14 (Unix) PHP/4.0.3pl1 mod_ssl/2.7.1
>OpenSSL/0.9.6):
>
>- start with "normal" Netscape client window loading IMP's startpage.
>- log in as usually
>- clicking on "Compose" on the left side opens the Compise window
>  (cancel the message for this test)
>- Resize the Netscape client window running IMP
>  (this is a typical user behaviour: go to IMP's startpage -- log in -- 
>  realize, that your window is to small for getting all without wrapping -- 
>  press the "Maximize Window" button -- continue working)
>- Netscape client refreshes all stuff, but obviously forgets about those
>  Javascript definitions of "menu.php3" on the left side:
>- Clicking on "Compose" results in nothing now.
>  (entering "javascript:" into the URL field is showing the JS errors)
>- Press the "Reload/Refresh" button and all is working again...
>
>This occurs with Netscape Communicator 4.76 (Unix/IRIX) and Netscape
>Communicator 4.7 (Windows NT) and does not occure with MS Internet Explorer 5.
>
>One more interesting thing: Watching the webservers access.log file I can see,
>that
>- resizing a Netscape window results accesses to the server
>- resizing a MS Internet Explorer window does not access the server at all.
>
>I played around with different
>  <meta http-equiv="no-cache" content="pragma">
>statements without success...
>
>Has anyone discovered this, too? Any idea of how to solve this?
>
>thanks a lot for a reply,
>  aleX.
>
>Chuck Hagenbuch wrote:
>
>>Quoting Alexander Dietz <alex@munich.sgi.com>:
>>
>>>I am using IMP 2.2.4 over a SSL connection and discovered the following
>>>problem (which does not occure every time): Clicking on "Compose" (or
>>>"Contacs") does not open a compose window; Netscape is reporting a 
>>>Javascript error: "open_compose_win not defined". The interesting thing is, 
>>>that "View Frame Source" comes up with all relevant functions.
>>>After changing all function definitions in imp/lib/js/* from
>>>  function any_name (args)
>>>to
>>>  function any_name(args)
>>>(i.e. deleting the space), all is running fine.
>>>
>>That sounds extremely unlikely. You might get that error when you click 
>>Compose before the page finishes loading; are you sure that's not it?
>>