Version: Apprunner Build: April 29th (1999042908) Platform: All Expected Results: After click on the toolbar icon such as bold, the I-beam cursor should function when typing. What I got: The focuse is lost forcing the user to click in the document to regain focus. Steps to reproduce: 1) Launch Apprunner. 2) From Task menu, select Editor. 3) Click in document to activate I beam cursor. Type some characters to verify that I-beam has focus. 4) Click on a toolbar icon like bold or italic. Now, try to type. Notice that the Ibeam cursor has lost it's focus.

Sounds like a focus problem. Assigning to Charley Manske, milestone set to M6

Now that I think about this, it is a general problem, not just for editor. Whenever a user clicks on chrome (menu or toolbar), the focus should return to the last window with content, such as the browser window, the sidebar, or the editor. This needs to be solved for all Communicator modules. Greg and Peter: Do you know who should own this problem?

Peter or Don: Did the general focus problem get assigned to someone in your groups? If so, what's the bug number?

hyatt and saari will be working on our end of it in M7. I don't know of any bug number offhand.

*** Bug 7845 has been marked as a duplicate of this bug. ***

*** Bug 6236 has been marked as a duplicate of this bug. ***

<adding myself to cc: list since this also affects mail compose>

Checked in 7/2/99. In EditorCommand.js, there are explicit contentWindow.focus() calls to return focus to the editor window after each UI action. We still should have some default behavior when a toolbar button is clicked and doesn't bring up other UI elements that must grab focus, such as a dialog or popup window, so we dont' have to set focus for EVERY command. This is tracked in another bug. But at least now we can set the focus explicitly whenever we want.

Based on the original description, this problem has been fixed in the July 6th build (1999070610).