Re: IPCStream landed in mozilla-central

On Sat, May 21, 2016 at 2:05 PM, Ben Kelly wrote: > > On May 21, 2016 9:44 AM, "Honza Bambas" wrote: > > If it's nsPipeInputStream then it's definitely alright. OTOH, we do > copy the memory, right? I was somehow hoping that you just expose the >

Re: IPCStream landed in mozilla-central

On May 21, 2016 9:44 AM, "Honza Bambas" wrote: > If it's nsPipeInputStream then it's definitely alright. OTOH, we do copy the memory, right? I was somehow hoping that you just expose the IPC-allocated buffers via your own implementation of nsIInputStream, avoiding coping to

Re: FF49a1: Page load of jumping points doesn't work like it should in Wikipedia

I guess they are going to track the DOM position rather than the scrolling offset. This does make sense, and we probably should do this as well. There are certain details we would need to take care. Not sure whether they are tracking the position based on the center or the top (or the bottom?).

Re: IPCStream landed in mozilla-central

On May 21, 2016 7:45 AM, "Honza Bambas" wrote: > But that doesn't mean "a fixed length input stream" - actually I may not even follow how you have translated this to you. Sorry, I was thinking a single OnDataAvailable call for the one IPC call just passing the stream.

Re: IPCStream landed in mozilla-central

On 5/21/2016 2:36, Ben Kelly wrote: On Fri, May 20, 2016 at 8:10 PM, Ben Kelly wrote: On Fri, May 20, 2016 at 11:09 AM, Ben Kelly wrote: On Fri, May 20, 2016 at 7:37 AM, Honza Bambas wrote: And I do! :) Actually any parent