From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050910 CentOS/1.7.10-1.4.2.centos4 Description of problem: Since upgrading to Mozilla 1.7.10, cursor keys occasionally stop working in the mail composition window. Cursor up, down, left, right, home, end are all inactive, changing window focus to another application and back to Mozilla usually resolves the problem. Version-Release number of selected component (if applicable): mozilla-1.7.10-1.4.2 How reproducible: Always Steps to Reproduce: 1. bring up new compose window Actual Results: Cursor keys do not work Expected Results: Cursor keys should move cursor Additional info: Cursor keys start working if compose window loses and then regains focus
Since this bugzilla report was filed, we have seriously upgraded Gecko-related packages, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their distribution available. Please, confirm to us that this bug is reproducible on the latest upgrade of the supported distribution (that's RHEL, or Fedora 7, 8, and Rawhide). Setting the bug to NEEDINFO. If I won't get confirmation of reproducability in 30 days, the bug will be closed as INSUFFICIENT_DATA. [This is mass-changing of bugs which seem to be too old and irrelevant anymore; we are sorry, if this bug should not be incldued.]
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.
Sorry for not responding. I am no longer using Mozilla or Seamonkey, so I cannot reproduce. I agree that this bug can be closed.