Unable to access DOM objects using standard OLE functions



Core Graveyard
Embedding: ActiveX Wrapper
14 years ago
6 years ago


(Reporter: Nick Hart, Assigned: Adam Lock)


Windows 2000

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4.1) Gecko/20031008
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031008

I have simple program that embeds the Mozilla ActiveX control into a java

When the document has been loaded, and the browser state is set to complete, I
retrieve the "all" property from the "document" interface. For some reason this
interface is blank and contains no methods or properties.

The same happens if I retrieve the "body" property from "document".

If I change my program to use the IE ActiveX control instead, I get the wanted
methods and properties (item(), length() etc from the "all" property, and
tagName(), getAttribute() from the "body" property).

There must be a difference between the Document object (where I can see the
methods and properties) and the "all" and "body" objects.

Reproducible: Always

Steps to Reproduce:
1. Wait for the page to render
2. Retrieve the "all" property
3. Check the methods which are defined on that property

Actual Results:  
I get a IDispatch object that has no methods or properties.

Expected Results:  
Like IE, I should get an object with the standard DOM methods.

I'm using SWT, a Java UI developed by IBM, which contains generic OLE support.

Comment 1

14 years ago
I'm not familiar with the ActiveX wrapper but document.all and document.body 
are not part of the standard DOM.

http://www.mozilla.org/docs/web-developer/upgrade_2.html#dom_unsupp may be 

Comment 2

14 years ago
Adam says on his site that the IE WebBrowser API has been implemented for the
control and that it has basic DOM functionality.

After looking at the C++ ActiveX source, document.body and document.all are
definately implemented. There must be some difference between how those controls
are defined and how the "document" and "webbrowser" controls are defined.

Comment 3

13 years ago
The control implements the standard DOM supported by Mozilla.

The Document.All method exists for binary compatibility with WebBrowser but does

Document.Body.OuterHTML works as expected.

A partial implementation of Document.All has been added to Mozilla; see bug
#248549. This may work in the next version of the control.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Component: Embedding: ActiveX Wrapper → Embedding: ActiveX Wrapper
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.