Re: e10s content processes and coordinate systems

2015-01-16 Thread kgupta
On Thursday, January 15, 2015 at 3:24:03 PM UTC-5, Handyman wrote: > and the compositor... I'm not sure how it compensates but it must use a > different mechanism for Compositors and CrossProcessCompositors, probably at > the Layer level?). I believe this happens in RenderFrameParent::BuildLayer,

Re: e10s content processes and coordinate systems

2015-01-15 Thread Robert O'Callahan
On Fri, Jan 16, 2015 at 9:24 AM, Handyman wrote: > I'm working on bug 1075670 ([e10s] event.screenX and event.screenY is > wrong), which exposes a hole in the e10s architecture. Quickly, the issue > is that the dom behavior in an e10s content process redefines "screen" > coordinates to be relati

e10s content processes and coordinate systems

2015-01-15 Thread Handyman
Hey all, I'm working on bug 1075670 ([e10s] event.screenX and event.screenY is wrong), which exposes a hole in the e10s architecture. Quickly, the issue is that the dom behavior in an e10s content process redefines "screen" coordinates to be relative to the tab contents instead of relative to