On 3/27/17 12:05 PM, Jack Moffitt wrote:
Yes, but since layout runs in parallel and is pretty fast, I'd think
the common case was that it would be done by the time it got the
second request.
I doubt layout is "pretty fast" on the scale involved here, which is
"hundreds of times per frame". Bu
> How would it handle the common failure mode I'd really like to address,
> where a page does:
>
> 1) Modify style.
> 2) Ask for layout data.
> 3) Modify style.
> 4) Ask for layout data.
>
> At step 4, will we just need to wait for the layout from step 2 to complete
> before we can start the ne
On 3/27/17 10:36 AM, Jack Moffitt wrote:
Responses to layout queries are just sent messages (if layout needed
invoking to answer them). It is possible to send them early as soon as
the relevant data has been computed. Servo does not do this currently
though. An initial implementation could just r
Responses to layout queries are just sent messages (if layout needed
invoking to answer them). It is possible to send them early as soon as
the relevant data has been computed. Servo does not do this currently
though. An initial implementation could just reply with the answer and
then keep running
Has there been any thought put into being able to satisfy queries for
layout information without doing a full style + layout flush on the
page? There are obviously things like CSS containment that can help
here, but it seems like it might be worth it to see whether we can
detect situations in
5 matches
Mail list logo
