With a pull/build on mac from today, I can't type in Composer. I can type in edit fields such as the urlbar. jst says this doesn't work on linux or windows.
Keywords: regression, smoketest
Target Milestone: --- → M16
is this possibly a dup of 40308?
granrose might be on to something. in #40308, I was seeing JS errors to the console. I'll try to get the console output for composer, and report back.
wacky, when I did -P editor, I got this error, but when I launched editor from messenger, it worked. (at least, it did once.) not 100% sure the two bugs are related, since I'm not seeing any JS errors to the console when editor fails to work.
nsEditorShell::OnEndDocumentLoad doesn't get called.
Putting on [dogfood+] radar.
HarishD and I have tracked it down a bit further: in nsWebShell.cpp, OnEndDocumentLoad... the difference in runtime between yesterday and today is that dlObserver-> OnEndDocumentLoad isn't getting called today (around line 1189) dlObserver is null, as is mDocLoaderObserver
I'm going to assign this to Adam for the time being -- Adam, do you have any idea as to what is going on?
Assignee: beppe → adamlock
Okay, so like I'm special :-] I can type in composer under any set of conditions, with either today's commercial or mozilla builds. I am on win95. Just a data point ...
And I couldn't reproduce the problem either!
Actually, I'm told that the issue is that the "first" time, you can't type in composer, but if you reset the focus once or twice, typing then works. Is that correct? (I'll shut up now).
Summary: can't type in Composer → can't type in Composer (initiallY)
For the initial window, I can't find any action that wakes up the editor -- tried inserting elements, resizing, etc. I can get an editor by starting a browser, open a file, then use File | Edit Page.
Yup..this happens only on the initial load [ verified on today's mac. build ]. Should we hold the tree closed for this? There seems to be a work around.
What do we need to do to verify this? I thought I found the culprit (the fix for 40308 I did find). But I just discovered that with or without my fix for 40308, I can run -editor and type in the edit window without a problem. Is there something special I need to do to see this problem?
Remove component.reg and restart mozilla [was able to reproduce on mac. but not on windows ]
after all the docshell changes, I'm not able to reproduce this anymore.
Summary: can't type in Composer (initiallY) → can't type in Composer (initially)
I cannot reproduce this after tossing everything. MacOS pull from 8pm-ish.
this is workingforme on linux, marking so.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → WORKSFORME
will verify after 40342 is fixed
Whiteboard: [dogfood+] → [dogfood+] will verify after 40342 is fixed
not sure what 40342 has to do with composer... typo?
verified on all platforms using 5/24 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.