From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.3+) Gecko/20010830 Netscape6/6.1b1 BuildID: 20010830 Pressing <ENTER> on the keyboard has no effect while in the Find and Replace (<CTRL>+<F>) dialogue in Composer. This is in contrast to the behaviour observed as a result of pressing <ENTER> while in the Find in this Page (<CTRL>+<F>) dialogue in Navigator, which reacts as normal and expected: by invoking a search for the text string entered. Reproducible: Always Steps to Reproduce: (1) Open a document to be edited in a new Composer window (2) Go Edit | Find and Replace (or, al- ternatively <CTRL>+<F>) (3) After entering a string in the ``Find what:'' field, hit <ENTER> on the keyboard Actual Results: No matter how many times one presses the <ENTER> key (nor what it is on the dialogue that is active) this has absolutely no effect as far as conducting a simple string- or key-search. Even pressing <TAB> five times to move the outlined/active status from the ``Find what:'' field to the [Find Next] button and pressing <ENTER> still has no effect at all. Pressing the <Space Bar> (with the [Find Next] button still active), does invoke the search, over and over. Expected Results: Pressing <ENTER> immediately after opening the Find and Replace panel and entering a string of text should invoke a search action on the Composer`s Find and Replace dialogue panel. There have been several similar issues discussed here concerning Composer`s the Find and Replace dialogue and its buttons, so at the risk of duplicating one of them, I report this contrast in behaviour between similar dialogues. Many computer users are used to keyboard shortcuts including the use of <ENTER> to invoke actions on dialogue panels.

-->cmanske

spam composer change

Guess we need to simply assign a default button!

The Find/Replace dialog is being changed by fix to bug 80805, so we'll wait until that is turned on to see if this is still a problem.

The dialog from bug 80805 *will* be checked in!

This issue is covered by bug 80805. *** This bug has been marked as a duplicate of 80805 ***

v