Fwd: Splitting inner and outer windows
R Kent James
kent at caspia.com
Tue Jan 26 18:42:44 UTC 2016
I saw this on platform, and it is one of those massive gecko changes
that will break us, but that should have a straightforward mapping into
Looking at the bug, I see changes in core code like:
- nsCOMPtr<nsIDOMWindow> DOMWindow;
+ nsCOMPtr<mozIDOMWindowProxy> DOMWindow;
Yes we'll have to accommodate this, but fixing gecko breakages is pretty
much our bread and butter activity these days. I have not looked deeper
to see if there are larger implications of this.
On 1/26/2016 1:48 AM, Gervase Markham wrote:
> Hi Thunderbird team,
> I take it you are aware of the below change? It has been suggested to me
> that this will have significant impact on Thunderbird.
> -------- Forwarded Message --------
> Subject: Splitting inner and outer windows
> Date: Thu, 21 Jan 2016 21:52:27 -0800
> From: Kyle Huey <me at kylehuey.com>
> To: dev-platform <dev-platform at lists.mozilla.org>
> Newsgroups: mozilla.dev.platform
> Early in the next release cycle I plan to land a patch that will remove
> nsPIDOMWindow in favor of two separate types for inner and outer windows
> (fittingly, called nsPIDOMWindowInner/nsPIDOMWindowOuter) I'll also make
> changes to the XPIDL interface hierarchy (effectively removing nsIDOMWindow
> and introducing two new base interfaces for inner and outer windows) to
> support this. When the dust settles places that today use nsPIDOMWindow or
> nsIDOMWindow will instead use a type that specifies, at compile time,
> whether we have an inner or outer window.
> The actual methods exposed on nsPIDOMWindow will be carried over in almost
> all cases. Splitting the interface itself, or nsGlobalWindow, apart will
> happen later.
> You can follow along in bug 1241764.
> - Kyle
> tb-planning mailing list
> tb-planning at mozilla.org
More information about the tb-planning