Closed Bug 183061 Opened 22 years ago Closed 15 years ago

WARNING: Should not try to set the focus on a disabled window

Categories

(SeaMonkey :: Composer, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: timeless, Unassigned)

Details

WARNING: Should not try to set the focus on a disabled window, file i:/build/mozilla/dom/src/base/nsGlobalWindow.cpp, line 2324 415 if ("gContentWindow" in window) 416 window.gContentWindow.focus(); 0 [native frame] 1 EditorRemoveTextProperty(property = "font", attribute = "color") ["chrome://editor/content/editorUtilities.js":416] propAtom = [xpconnect wrapped nsIAtom @ 0xccc0dc0] this = [object ChromeWindow @ 0xb8d7700] 2 EditorResetFontAndColorAttributes() ["chrome://editor/content/editor.js":537] bodyelement = undefined editor = undefined this = [object ChromeWindow @ 0xb8d7700] 3 anonymous() ["chrome://messenger/content/messengercompose/MsgComposeCommands.js":217] showFormat = undefined event = undefined this = [object Object] 4 [native frame] GlobalWindowImpl::Focus(GlobalWindowImpl * const 0x0c146ddc) line 2325 XPTC_InvokeByIndex(nsISupports * 0x0c146ddc, unsigned int 65, unsigned int 0, nsXPTCVariant * 0x0012e16c) line 106 XPCWrappedNative::CallMethod(XPCCallContext & {...}, XPCWrappedNative::CallMode CALL_METHOD) line 2016 + 42 bytes XPC_WN_CallMethod(JSContext * 0x01103010, JSObject * 0x045c1888, unsigned int 0, long * 0x0c6651d4, long * 0x0012e410) line 1283 + 14 bytes js_Invoke(JSContext * 0x01103010, unsigned int 0, unsigned int 0) line 839 + 23 bytes js_Interpret(JSContext * 0x01103010, long * 0x0012ed2c) line 2803 + 15 bytes js_Invoke(JSContext * 0x01103010, unsigned int 0, unsigned int 2) line 856 + 13 bytes nsXPCWrappedJSClass::CallMethod(nsXPCWrappedJSClass * const 0x0c57aa58, nsXPCWrappedJS * 0x0c57aac0, unsigned short 3, const nsXPTMethodInfo * 0x03a955c8, nsXPTCMiniVariant * 0x0012f270) line 1200 + 22 bytes nsXPCWrappedJS::CallMethod(nsXPCWrappedJS * const 0x0c57aac0, unsigned short 3, const nsXPTMethodInfo * 0x03a955c8, nsXPTCMiniVariant * 0x0012f270) line 430 PrepareAndDispatch(nsXPTCStubBase * 0x0c57aac0, unsigned int 3, unsigned int * 0x0012f320, unsigned int * 0x0012f310) line 115 + 31 bytes SharedStub() line 139 nsMsgCompose::CloseWindow(nsMsgCompose * const 0x0c579cb8, int 1) line 1201 nsMsgComposeSendListener::OnStopCopy(nsMsgComposeSendListener * const 0x0cba63d8, unsigned int 0) line 2801 nsMsgComposeAndSend::NotifyListenerOnStopCopy(nsMsgComposeAndSend * const 0x0cba5fd0, unsigned int 0) line 3784 CopyListener::OnStopCopy(CopyListener * const 0x0cb895f8, unsigned int 0) line 159 nsMsgCopyService::ClearRequest(nsCopyRequest * 0x0cbee4d8, unsigned int 0) line 177 nsMsgCopyService::NotifyCompletion(nsMsgCopyService * const 0x0c02ce78, nsISupports * 0x0ccd5b38, nsIMsgFolder * 0x03ed3c44, unsigned int 0) line 549 nsImapMailFolder::OnCopyCompleted(nsISupports * 0x0ccd5b38, unsigned int 0) line 6554 nsImapMailFolder::OnStopRunningUrl(nsImapMailFolder * const 0x03ed3cb0, nsIURI * 0x0c650ddc, unsigned int 0) line 4509 nsUrlListenerManager::BroadcastChange(nsIURI * 0x0c650ddc, nsUrlNotifyType nsUrlNotifyStopRunning, unsigned int 0) line 111 nsUrlListenerManager::OnStopRunningUrl(nsUrlListenerManager * const 0x0c5b12a8, nsIMsgMailNewsUrl * 0x0c650ddc, unsigned int 0) line 124 + 18 bytes nsMsgMailNewsUrl::SetUrlState(nsMsgMailNewsUrl * const 0x0c650ddc, int 0, unsigned int 0) line 137 nsImapMailFolder::SetUrlState(nsImapMailFolder * const 0x03ed3cf0, nsIImapProtocol * 0x0bcda348, nsIMsgMailNewsUrl * 0x0c650ddc, int 0, unsigned int 0) line 5662 + 23 bytes XPTC_InvokeByIndex(nsISupports * 0x03ed3cf0, unsigned int 27, unsigned int 4, nsXPTCVariant * 0x0c458da0) line 106 EventHandler(PLEvent * 0x0c591398) line 567 + 41 bytes PL_HandleEvent(PLEvent * 0x0c591398) line 644 + 10 bytes PL_ProcessPendingEvents(PLEventQueue * 0x00fc9ce8) line 574 + 9 bytes nsEventQueueImpl::ProcessPendingEvents(nsEventQueueImpl * const 0x0100bfe0) line 388 + 12 bytes nsWindow::DispatchPendingEvents() line 3662 nsWindow::ProcessMessage(unsigned int 261, unsigned int 52, long -536543231, long * 0x0012fc48) line 3900 nsWindow::WindowProc(HWND__ * 0x00160400, unsigned int 261, unsigned int 52, long -536543231) line 1339 + 27 bytes USER32! 77e13eb0() USER32! 77e1401a() USER32! 77e13f0f() nsAppShellService::Run(nsAppShellService * const 0x0105a950) line 472 main1(int 4, char * * 0x002844c0, nsISupports * 0x00276f08) line 1541 + 32 bytes main(int 4, char * * 0x002844c0) line 1902 + 37 bytes mainCRTStartup() line 338 + 17 bytes KERNEL32! 77e87903() Steps: run mozilla configure password protected smtp server and imap server. connect to imap server (enter imap password), read a bugmail, reply, select a recipient, send (enter smtp password), <problem near here>
Product: Browser → Seamonkey
Assignee: cmanske → nobody
QA Contact: sujay → composer
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.