Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have DisplayListBuilder keep track of its own AuxiliaryListsBuilder #574

Closed
vvuk opened this issue Nov 18, 2016 · 1 comment
Closed

Have DisplayListBuilder keep track of its own AuxiliaryListsBuilder #574

vvuk opened this issue Nov 18, 2016 · 1 comment

Comments

@vvuk
Copy link
Contributor

@vvuk vvuk commented Nov 18, 2016

Now that everything is flattened, it doesn't look like there's any need to keep track of a separate aux lists builder and pass it around -- the DisplayListbBuilder should be able to keep track of one internally and use it as needed. @mrobinson any reason to not do this?

@mrobinson
Copy link
Member

@mrobinson mrobinson commented Nov 18, 2016

@vvuk Definitely correct. I was planning on doing this after landing: #567

mrobinson added a commit to mrobinson/webrender that referenced this issue Nov 24, 2016
This makes it a bit less complicated to use the WebRender API and hides
some details that might change later.

Fixes servo#574.
mrobinson added a commit to mrobinson/webrender that referenced this issue Nov 25, 2016
This makes it a bit less complicated to use the WebRender API and hides
some details that might change later.

Fixes servo#574.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.