134841 - After Composer window creation lot of menu items remain unitialized

Status: VERIFIED WORKSFORME

(SeaMonkey :: Composer, defect)

Description

[Sergei Dolgov]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (BeOS; U; BeOS BePC; en-US; rv:0.9.9+) Gecko/20020328
BuildID:    

In "fresh"  composer window even such menu Item as File->Open stays disabled -
until you enter some character in edit window. If composer is opened with
content (e.g. via "View Page in Composer") - all is OK.


Reproducible: Always
Steps to Reproduce:
1.Go to "Tasks" and click "Composer"
2.Immediatelly click "File" menu item.
3.Look at disabled menu items

It seems related to whole set of those messy focus problems in Mozilla
(BeZilla?). Though, in this case remedy is simple - adding one line in editor
javascript code. - mozilla/editor/ui/composer/content/editor.js

function EditorStartup(editorType, editorElement)
{
******
 SetupComposerWindowCommands();
++window.focus();

Comment 1

[sujay]

--> cmanske

Comment 2

[Charles Manske]

I don't see this problem in Windows 2000.
Sujay: Can you confirm on any other platform?
I don't see any reason not to add the suggested "window.focus()" call if this 
fixes the problem for BeOS.

Comment 3

[sujay]

I cannot reproduce this using 4/5 trunk build on Win 98

Comment 4

[Sergei Dolgov]

I think there  is no need to test it on any Wintel platform. I don't know neither WinApi, nor specifics of Winzilla but suspect that both windows - navigator and composer are "chidlren" of same handler. At least you may notice, that in Win builds editor field gets focused automatically - after Composer creation - typing immediatelly enters text there.t isn't the case in BeOS build.And this is the difference.

Comment 5

[Daniel Furrer]

I can't reproduce this bug. (Using mozilla 1.3b nightly: 2003020711)

Comment 6

[Sergei Dolgov]

latest builds work ok even with BeOS:)

Comment 7

[Kathleen :Brade]

v