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" <mbrub...@mozilla.com> wrote: > 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 instead of (or in addition to?) the display list. The > future would contain sort of identifier that corresponds to an image > request. Each time layout runs, any "image future" fragment would check to > see if its request was now finished. When any image load completes, we > could trigger a layout pass that triggers these checks. (This could use a > new RestyleDamage flag, or maybe just make sure these fragments have an > existing flag like REPAINT set for as long as they contain an unfulfilled > future.) > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
