145259 - DOM inspector does not show attributes of embed or applet element if java running

Status: RESOLVED DUPLICATE of bug 59686

(Other Applications :: DOM Inspector, defect)

Description

[Kevin C.]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2)
Gecko/20020510
BuildID:    2002051006

When looking at the embed or applet element in the DOM inspector with java
enabled, no attributes are shown. Also the PARAM element children of an APPLET
element do not show properly either.
If java is disabled, then they can be inspected fine.

Reproducible: Always
Steps to Reproduce:
1.Enable Java
2.Open a page with a Java applet in DOM Inspector
3.Navigate to the applet or embed element on the page

Actual Results:  The window displaying attributes is blank for the embed or
applet element, and shows "target" as the only member for the param element.

Expected Results:  It should have shown the attributes just like it does with
Java disabled.

Comment 1

[Kevin C.]

Note: I have Java version 1.3.1

I noticed that if you view the page first with Java disabled, then when you
enable Java and reload you can still see the attributes. You must view the page
first with Java enabled.

I also noticed that when reproducing this bug, it can crash the browser. If you 

1.View the page with Java enabled
2.Navigate to the APPLET element to view its attributes
3.Disable Java
4.Reload the page
5.Navigate to the APPLET element to view its attributes
6.Enable java
7.Reload the page
8.Navigate to the APPLET element to view its attributes

it appears to crash the browser fairly reliably.
Talkback ID of following those exact steps is TB6384571K.
Talkback IDs that appear to be the same bug, before I isolated the exact steps
to reproduce are TB6383926E and TB6383471X

Comment 2

[Boris Zbarsky [:bzbarsky]]

stephend, would you get the stack?  TB6384571K

Comment 3

[[e-mail] (gone - use [e-mail] instead)]

Nothing comes up for that stack trace, sorry.  If possible, please get submit
another ID, because the receiving servers were down a couple of days.

Comment 4

[Kevin C.]

Followed the 8 steps to reproduce crash again and submitted talkback ID
TB6400141Q at 5/17/2002 6:42PM (Central time) description is "Reproducing bug #
145259"

Comment 5

[[e-mail] (gone - use [e-mail] instead)]

JSJ_HashTableRawLookup
[d:\builds\seamonkey\mozilla\js\src\liveconnect\jsj_hash.c, line 202]
jsj_WrapJavaObject
[d:\builds\seamonkey\mozilla\js\src\liveconnect\jsj_JavaObject.c, line 171]
jsj_ConvertJavaObjectToJSValue
[d:\builds\seamonkey\mozilla\js\src\liveconnect\jsj_convert.c, line 862]
JSJ_ConvertJavaObjectToJSValue
[d:\builds\seamonkey\mozilla\js\src\liveconnect\jsj.c, line 865]
nsJVMManager::WrapJavaObject
[d:\builds\seamonkey\mozilla\modules\oji\src\nsJVMManager.cpp, line 441]
nsHTMLAppletElementSH::GetPluginJSObject
[d:\builds\seamonkey\mozilla\dom\src\base\nsDOMClassInfo.cpp, line 5080]
nsHTMLExternalObjSH::PostCreate
[d:\builds\seamonkey\mozilla\dom\src\base\nsDOMClassInfo.cpp, line 4965]
XPCWrappedNative::GetNewOrUsed
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 402]
XPCWrappedNative::GetNewOrUsed
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 292]
XPCConvert::NativeInterface2JSObject
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcconvert.cpp, line 1061]
XPCConvert::NativeData2JS
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcconvert.cpp, line 462]
XPCWrappedNative::CallMethod
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 2121]
XPC_WN_CallMethod
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp,
line 1267]
js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 790]
js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2744]
js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 806]
js_InternalInvoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 881]
JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3426]
nsJSContext::CallEventHandler
[d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 1019]
nsJSEventListener::HandleEvent
[d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 182]
nsEventListenerManager::HandleEventSubType
[d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line
1218]
nsEventListenerManager::HandleEvent
[d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line
1821]
nsXULElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3461]
nsTreeSelection::FireOnSelectHandler
[d:\builds\seamonkey\mozilla\layout\xul\base\src\tree\src\nsTreeSelection.cpp,
line 743]
nsTreeSelection::Select
[d:\builds\seamonkey\mozilla\layout\xul\base\src\tree\src\nsTreeSelection.cpp,
line 369]
XPTC_InvokeByIndex
[d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp,
line 106]
XPCWrappedNative::CallMethod
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 2027]
XPC_WN_CallMethod
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp,
line 1267]
js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 790]
js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2744]
js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 806]
js_InternalInvoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 881]
JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3426]
nsJSContext::CallEventHandler
[d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 1019]
nsJSEventListener::HandleEvent
[d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 182]
nsXBLPrototypeHandler::ExecuteHandler
[d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeHandler.cpp, line 447]
DoContextMenu
[d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLContextMenuHandler.cpp, line 105]
nsXBLMouseHandler::MouseDown
[d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLMouseHandler.cpp, line 124]
nsEventListenerManager::HandleEvent
[d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line
1307]
nsXULElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3461]
PresShell::HandleEventInternal
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 6110]
PresShell::HandleEvent
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 6028]
nsViewManager::HandleEvent
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 2076]
nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 306]
nsViewManager::DispatchEvent
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1887]
HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 83]
nsWindow::DispatchEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 869]
nsWindow::DispatchWindowEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 886]
nsWindow::DispatchMouseEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 4713]
ChildWindow::DispatchMouseEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 4968]
nsWindow::ProcessMessage
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3630]
nsWindow::WindowProc
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 1131]
USER32.DLL + 0x1b60 (0x77e11b60)
USER32.DLL + 0x1cca (0x77e11cca)
USER32.DLL + 0x83f1 (0x77e183f1)
nsAppShellService::Run
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp, line 451]
main1 [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1473]
main [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1809]
WinMain [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1827]
WinMainCRTStartup()
KERNEL32.DLL + 0xd326 (0x77e8d326) 

Comment 6

[Boris Zbarsky [:bzbarsky]]

confirmed; hewitt's call as to whether this belongs in liveconnect land...

Comment 7

[Corrado Berti]

is this a dupl of bug 59686 ?

Comment 8

[Christopher Aillon (sabbatical, not receiving bugmail)]

I think it is.

*** This bug has been marked as a duplicate of 59686 ***