Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMake layout queries walk the cached flow tree instead of the display list #3790
Comments
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Oct 30, 2014
Instead of looking at the display tree, have ContentBox(es)Query consult the flow tree. This allow optimizing away parts of the display tree later. To do this we need to be more careful about how we send reflow requests, only querying the flow tree when possible. Fixes servo#3790.
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Oct 30, 2014
Instead of looking at the display tree, have ContentBox(es)Query consult the flow tree. This allow optimizing away parts of the display tree later. To do this we need to be more careful about how we send reflow requests, only querying the flow tree when possible. Fixes servo#3790.
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Oct 31, 2014
Instead of looking at the display tree, have ContentBox(es)Query consult the flow tree. This allow optimizing away parts of the display tree later. To do this we need to be more careful about how we send reflow requests, only querying the flow tree when possible. Fixes servo#3790.
bors-servo
pushed a commit
that referenced
this issue
Nov 3, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This will help issues like #1716 and allow us to perform layout using ReflowForQuery instead of ReflowForDisplay in many cases, which will avoid building the display list.