228476 - When writing a blog article, the arrow, HOME, and END keys do not work in input textarea

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[woddfellow2]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 MultiZilla/1.5.0.4h
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 MultiZilla/1.5.0.4h

When trying to write an article, the arrow, HOME, and END keys do not work.
<sarcasm>Great when trying to fix a typo.</sarcasm>

Reproducible: Always

Steps to Reproduce:
1. Go to <A HREF="http://www.ipadder.com/">http://www.ipadder.com/</a>.
2. Log in.
3. Click "new article".
4. In the content box, type some text, then try to press an arrow key.
5. It won't work.

Comment 1

[HJ]

a) we need a test account, don't have one
b) disable MultiZilla with "QPrefs/Extension Management/MultiZilla" and try to
reproduce this bug without MultiZilla enabled.
c) is this limited to this site only or do you have the same problem on other
sites? 

Comment 2

[HJ]

I've setup a test account (mozilla). Please e-mail me for the corresponding
password (my e-mail address is used) in case you want to verify this bug report.

This WORKSFORME with using mozilla 2003110115 and MultiZilla v1.6.0.0 revision D

note: I couldn't find that 'new article' link, but 'add article' only...

Comment 3

[Timothy Miller]

I encounter this very same bug when composing emails on hotmail.  Actually, I
have encountered this problem numerous other places, but I finally got off my
duff and decided to report the problem while I was using hotmail.

Comment 4

[Timothy Miller]

Oops... forgot version number.  I'm using Mozilla version:  Mozilla/5.0 (X11; U;
Linux i686; en-US; rv:1.7.3) Gecko/20040919

Comment 5

[HJ]

Timothy, do you use MultiZilla and another question is, do you see javascript
errors on your javascript console when this happens? Oh, and one more thing, is
this reproducable?

Please verify your settings on Mozilla's debug preference panel. 
You should see something like this:
[v] Enable JavaScript dump() output
[v] Show strict JavaScript warnings
[v] Show chrome JavaScript errors and warnings

Comment 6

[mmortal03]

This may be the same as or related to Bug 220900.

I often get both of these to break at the same time.

Comment 7

[Wayne Mery (:wsmwk)]

Tim, woddfellow, 
has this ever gone away?

see also bug 259007, bug 264037.
(forget about bug 220900 - it's a mess)

Comment 8

[brian maniere]

Holy schmoly!   this has been going on since 2003??  I only started nocing the probalem a couple months ago.

I'm confirming this bug still exists in the latest official release (1.5.0.4) and it's really annoying.  I would say it happens to me at least once a day on average.  I found a workaround on the mozillazine forums -- if you hit F1 to set the focus on a new window, the problem goes away once you bring focus back to the original brower window.  I haven't tested this extensively, but it worked just now, the latest time I ran into this bug.

This is a major usability issue that I'm sure turns off a huge number of users, so I hope it gets the prompt attention that it deserves.

See Bug 314683 and several others for a probable duplicates.

Comment 9

[Shawn M. Jones]

I have collected all of the bugs that display these symptoms under Bug 389768.

Comment 10

[Tony Mechelynck [:tonymec]]

Bug 389768 has now been resolved WORKSFORME (reporter hasn't seen the behaviour since Firefox 2.0.0.12).

If anyone still sees this in a current build of SeaMonkey (2.0.14 or later, preferably 2.1 or later), please speak up or this bug will be closed too.

Comment 11

[Philip Chee]

The focus code has been rewritten several times and the latest Focus Manager code is a total rewrite by Neil Deakin. Any similar issues today are highly unlikely to have the same cause as this bug. Closing already.