Display lists are serializable, so it seems difficult to store futures
there. The Fragment seems like the natural place for them. I concur with
mbrubeck that some kind of future seems like the right solution here.
Patrick
On May 25, 2016 6:35 PM, "Matt Brubeck" wrote:
> In ancient double-digit-i
In ancient double-digit-issue times, our forefather brson suggested that we
could store some sort of promise or future in the display list, for images
pending load:
https://github.com/servo/servo/issues/43
Would something like this work? It might make sense to store the futures
in the flow tree i
I'm in the process of removing all traces of synchronous image loading
from Servo, building on top of one of this quarter's NCSU projects. I'm
dealing with a test failure right now where I understand the problem,
but I'm currently stumped on how to solve it, so I'm open to ideas.
THE PROBLEM:
3 matches
Mail list logo
