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,
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
2 matches
Mail list logo
