[Tickets #5237] Re: reply to and related buttons

[bugs at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=5237
-----------------------------------------------------------------------
 Ticket             | 5237
 Updated By         | john at s9co.com
 Summary            | reply to and related buttons
 Queue              | Horde Base
 Version            | 3.1.3
 Type               | Enhancement
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


john at s9co.com (2007-04-10 20:59) wrote:

When I click on them nothing happens. I have to close one instance of
webmail first then reload the screen to get functionality back for the
following items (I haven't tested others since they are not normally used
by me):

Delete | Reply | Reply to All | Forward

Also the top menu for Compose.

I know from coding webpages if you use the same same name for different
things it can cause problems. Sorry if I didn't describe it well but
that's what has happened before. I had to generate unique variable names
and how I did it was by doing what I described initially.

So if it doesn't apply to Horde please ignore, but what I was trying to
describe was a valid solution to situations I've encountered before.

Thank you for looking into it, please let me know if there's anything else
i can provide.

> Can you explain why this is in the Horde queue instead of IMP?
>
>> When I have two different webmail accounts open (different servers)
>> but in the same browser the reply to script (and other "new window"
>> buttons) fail because there is more than one instance calling the
>> same script.
>
> Please be more specific than "fail". What happens? Do you get a 
> javascript error?
>
>> In the scripts providing functionality there might be a var or
>> function call like:
>>
>> var x = 1
>> function y
>>
>> But since it is the same for both instances = ERROR
>
> No, that's not how javascript works.