[Tickets #14267] Forward / Reply / New message results in popup "Loading..."
noreply at bugs.horde.org
noreply at bugs.horde.org
Wed Feb 24 15:23:45 UTC 2016
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: https://bugs.horde.org/ticket/14267
------------------------------------------------------------------------------
Ticket | 14267
Created By | horde-support at inetspec.com
Summary | Forward / Reply / New message results in popup
| "Loading..."
Queue | IMP
Version | 6.2.12
Type | Bug
State | Unconfirmed
Priority | 3. High
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
horde-support at inetspec.com (2016-02-24 15:23) wrote:
Any attempt to Forward, Reply, or create a New Message using IE11 (or
Edge) results in the popup window hanging with the "Loading..."
message indefinitely.
Server Environment:
CentOS 6 - Apache - MySQL - PHP 5.3.3
Horde Groupware Webmail Edition 5.2.12 (installed via PEAR)
Mail (imp) 6.2.12
Browser: IE11 (also Edge), have not tested on IE8 - IE10
Note: Does NOT occur on Firefox or Chrome and is not limited to any
single computer installation. We have tested on Windows 8.1 Pro,
Windows 7, and Windows 10 machines.
Using the Debugger in IE shows multiple errors occuring through the
prototype.js file. The last one being fatal and stopping the script.
I will list the errors in the order that they occur:
Line 2092 InvalidCharacter
Line 5032 SyntaxError
Line 5045 SyntaxError
Line 969 Unable to get property 'observe' of undefined or null reference
The Call Stack at the point of the final error looks like this:
Unable to get property 'observe' of undefined or null reference
[Main Thread]
Anonymous function [Line: 969, Col: 7], prototype.js
Anonymous function [Line: 1270, Col: 9], prototype.js
invoke [Line: 968, Col: 5], prototype.js
DimpCompose.onDomLoad [Line: 1411, Col: 13], compose-dimp.js
Anonymous function [Line: 7206, Col: 7], prototype.js
fireEvent_DOM [Line: 7066, Col: 5], prototype.js
fire [Line: 7055, Col: 5], prototype.js
_methodized [Line: 456, Col: 7], prototype.js
fireContentLoadedEvent [Line: 7241, Col: 5], prototype.js
[Async Call]
Anonymous function [Line: 7269, Col: 5], prototype.js
Global code [Line: 7231, Col: 2], prototype.js
We understand that Firefox / FireBug are preferred for this type of
troubleshooting. However, these errors simply do not surface when
using either Firefox or Chrome.
We have attached a screen snippet and will be happy to provide any
further information we can in order to track down this problem.
Thanks,
Jon
horde-support at inetspec.com (2016-02-24 15:23) uploaded:
969-UnableToGetProperty-FATAL.PNG
https://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=969-UnableToGetProperty-FATAL.PNG&ticket=14267&fn=%2F969-UnableToGetProperty-FATAL.PNG
More information about the bugs
mailing list