[Tickets #10626] Re: textarea fields doesn't scroll up under IE9

bugs at horde.org bugs at horde.org
Wed Oct 12 19:21:41 UTC 2011


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

Ticket URL: http://bugs.horde.org/ticket/10626
------------------------------------------------------------------------------
  Ticket             | 10626
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | textarea fields doesn't scroll up under IE9
  Queue              | Horde Base
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-10-12 13:21) wrote:

> I understand that this could be a problem with a browser. I don't  
> have much sites with Win7/IE9. Most of them run Windows XP/IE8  
> currently, however in a year or two I suspect most of them will be  
> running the latest from Microsoft. And not to be able to perform  
> such simple tasks as browsing email text is a real showstopper to  
> implement webmail which is based on Horde. So all in all this is  
> pretty serious issue.

Except it's not.  A serious issue is one that is reproducible 100% of  
the time; this one isn't. (I'd also guess that the majority of people  
use the mouse to scroll, not the keyboard, so this would theoretically  
not affect them)

> Not sure why this happens in Whups though. It is happening right now  
> during me writing this.

Then this *has* to be a browser bug.  Because the javascript is  
completely different between imp and whups, so it is not something  
related to, for example, javascript events.

At a minimum, you will have to track this down.  We (I) can't fix  
anything if I can't reproduce.

As to where to start: I have no idea.  The only event watching the  
compose screen deals with forwarding messages, which you are not  
doing.  And you are not using HTML compose mode, so that, although a  
likely culprit (and also something that we can do nothing about), is  
not at issue here.





More information about the bugs mailing list