Consider requiring GetParentObject to return a ParentObject

NEW
Unassigned

Status

()

Core
DOM
4 years ago
4 years ago

People

(Reporter: bz, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

In bug 887533 we had to add a bunch of includes to headers because bindings code has no way to know what the return type of GetParentObject is.

I think we should consider requiring that GetParentObject return a ParentObject struct, and make all GetParentObject implementations that need extra includes not inline....  It'll mean one extra OOL call during wrapping, and is a bit more user-hostile, but that might be ok.
Flags: needinfo?(peterv)
As long as we don't make ParentObject constructors explicit, fine by me :-).
Flags: needinfo?(peterv)
You need to log in before you can comment on or make changes to this bug.