Bug 20752 – On Windows, many of the important COM intefaces are either missing or not implemented.

• Status: RESOLVED
• Resolution: WONTFIX
• Component: Platform

[Matt]

WebKit exposes some of its API via COM interfaces on Windows.  Unfortunately some of the most important interfaces are either not implemented (they return E_NOTIMPL), or are simply not exposed via the COM interfaces.

E_NOTIMPL:
- string IDOMElement::tagName()
- IDOMNodeList IDOMNode::childNodes()

Missing from the COM interfaces:
- int IDOMHTMLElement::offsetLeft()
- int IDOMHTMLElement::offsetTop()
- int IDOMHTMLElement::offsetWidth()
- int IDOMHTMLElement::offseHeight()
- int IDOMHTMLElement::scrollLeft()
- int IDOMHTMLElement::scrollTop()
- IDOMHTMLElement IDOMHTMLElement::offsetParent();

It would be really nice if the interfaces that were actually exposed were implemented, and if those that aren't on the COM wrappers could be exposed.

[Adam Roben (:aroben)]

We need to turn on our autogenerated COM DOM bindings!

[Denis]

Should we await that WebKit COM interfaces on Windows will be fully implemented in the near future?

[Adam Roben (:aroben)]

(In reply to comment #2)
> Should we await that WebKit COM interfaces on Windows will be fully implemented
> in the near future?

The COM API is being implemented as Safari or some other client finds a need for each function. If you want to see certain interfaces implemented, you are free to submit a patch doing so.

[Ahmad Saleem]

Is it applicable for 'win-cairo' port?

[Fujii Hironori]

Windows WebKit1 was removed. Closed.