Reply broken in dimp-git

[Chuck Hagenbuch]

Right now in DIMP-git replies aren't populating the to: address or the  
subject. The body is generated correctly.

-chuck

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Michael M Slusarz-2]

Quoting Chuck Hagenbuch <chuck@...>:

> Right now in DIMP-git replies aren't populating the to: address or  
> the subject. The body is generated correctly.

I don't see this.  I have pushed some changes sitting on my machine,  
but those commits shouldn't affect reply behavior.  Possibly a js  
caching issue?  I change the name of some of the compose DOM elements  
in the last week so that may have affected things.

michael

--
___________________________________
Michael Slusarz [slusarz@...]


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Chuck Hagenbuch]

Quoting Michael M Slusarz <slusarz@...>:

> Quoting Chuck Hagenbuch <chuck@...>:
>
>> Right now in DIMP-git replies aren't populating the to: address or  
>> the subject. The body is generated correctly.
>
> I don't see this.  I have pushed some changes sitting on my machine,  
> but those commits shouldn't affect reply behavior.  Possibly a js  
> caching issue?  I change the name of some of the compose DOM  
> elements in the last week so that may have affected things.

That sounds like the right area, but doing a pull, emptying my cache,  
and trying again and I still have the same problem.

-chuck

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Michael J. Rubinsky]

Quoting Chuck Hagenbuch <chuck@...>:

> Quoting Michael M Slusarz <slusarz@...>:
>
>> Quoting Chuck Hagenbuch <chuck@...>:
>>
>>> Right now in DIMP-git replies aren't populating the to: address or  
>>> the subject. The body is generated correctly.
>>
>> I don't see this.  I have pushed some changes sitting on my  
>> machine, but those commits shouldn't affect reply behavior.  
>> Possibly a js caching issue?  I change the name of some of the  
>> compose DOM elements in the last week so that may have affected  
>> things.
>
> That sounds like the right area, but doing a pull, emptying my  
> cache, and trying again and I still have the same problem.

I've been seeing this also for the last few days.  I'm getting a  
"Element is null" error on line 4066 in prototype.js.


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk@...

"Time just hates me. That's why it made me an adult." - Josh Joplin



--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Michael J. Rubinsky]

Quoting Michael Rubinsky <mrubinsk@...>:

> Quoting Chuck Hagenbuch <chuck@...>:
>
>> Quoting Michael M Slusarz <slusarz@...>:
>>
>>> Quoting Chuck Hagenbuch <chuck@...>:
>>>
>>>> Right now in DIMP-git replies aren't populating the to: address  
>>>> or  the subject. The body is generated correctly.
>>>
>>> I don't see this.  I have pushed some changes sitting on my  
>>> machine, but those commits shouldn't affect reply behavior.    
>>> Possibly a js caching issue?  I change the name of some of the  
>>> compose DOM elements in the last week so that may have affected  
>>> things.
>>
>> That sounds like the right area, but doing a pull, emptying my  
>> cache, and trying again and I still have the same problem.
>
> I've been seeing this also for the last few days.  I'm getting a  
> "Element is null" error on line 4066 in prototype.js.

... and if it helps, I just got a "doActionComplete: TypeError-element  
is null (Line #4066)" in  a javascript alert when replying to an email.


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk@...

"Time just hates me. That's why it made me an adult." - Josh Joplin



--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Michael M Slusarz-2]

Quoting Michael Rubinsky <mrubinsk@...>:

> Quoting Michael Rubinsky <mrubinsk@...>:
>
>> Quoting Chuck Hagenbuch <chuck@...>:
>>
>>> Quoting Michael M Slusarz <slusarz@...>:
>>>
>>>> Quoting Chuck Hagenbuch <chuck@...>:
>>>>
>>>>> Right now in DIMP-git replies aren't populating the to: address  
>>>>> or  the subject. The body is generated correctly.
>>>>
>>>> I don't see this.  I have pushed some changes sitting on my  
>>>> machine, but those commits shouldn't affect reply behavior.    
>>>> Possibly a js caching issue?  I change the name of some of the  
>>>> compose DOM elements in the last week so that may have affected  
>>>> things.
>>>
>>> That sounds like the right area, but doing a pull, emptying my  
>>> cache, and trying again and I still have the same problem.
>>
>> I've been seeing this also for the last few days.  I'm getting a  
>> "Element is null" error on line 4066 in prototype.js.
>
>
> ... and if it helps, I just got a "doActionComplete:  
> TypeError-element is null (Line #4066)" in  a javascript alert when  
> replying to an email.

Fixed (will push the commit shortly).

michael

--
___________________________________
Michael Slusarz [slusarz@...]


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...