Re: Having more control over when an IPDL message is compressed

2014-03-26 Thread Boris Zbarsky
On 3/26/14 10:13 PM, Botond Ballo wrote: The name "compression" is unfortunate here. It took me some time to understand what the real issue is. Agreed. (Any ideas for a better word? For me 'supersede' comes to mind, as in a newer message supersedes an older one so the older one can be dropped,

Re: Having more control over when an IPDL message is compressed

2014-03-26 Thread Botond Ballo
> The name "compression" is unfortunate here. It took me some time to > understand what the real issue is. Agreed. (Any ideas for a better word? For me 'supersede' comes to mind, as in a newer message supersedes an older one so the older one can be dropped, but I don't think that would be very

Re: Having more control over when an IPDL message is compressed

2014-03-25 Thread Kyle Huey
On Tue, Mar 25, 2014 at 6:18 AM, Botond Ballo wrote: > Hello dev-platform, > > I recently fixed an APZ bug [1] that was caused by an IPDL message, > PBrowser::UpdateFrame, being compressed when it shouldn't have been. > > I think the compression was correct back when we didn't have subframe > scro

Re: Having more control over when an IPDL message is compressed

2014-03-25 Thread Trevor Saunders
On Mon, Mar 24, 2014 at 03:18:19PM -0700, Botond Ballo wrote: > Hello dev-platform, > > I recently fixed an APZ bug [1] that was caused by an IPDL message, > PBrowser::UpdateFrame, being compressed when it shouldn't have been. > > I think the compression was correct back when we didn't have subfr

Having more control over when an IPDL message is compressed

2014-03-24 Thread Botond Ballo
Hello dev-platform, I recently fixed an APZ bug [1] that was caused by an IPDL message, PBrowser::UpdateFrame, being compressed when it shouldn't have been. I think the compression was correct back when we didn't have subframe scrolling, and so all messages pertained to the same frame, in which c