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

decouple script from compositor, route through layout #517

Merged
merged 5 commits into from Jun 17, 2013

Conversation

@tikue
Copy link

tikue commented Jun 14, 2013

communicate via layout
refactor channel wrappers from *Task --> *Chan

@tikue
Copy link
Author

tikue commented Jun 14, 2013

r? @pcwalton

some of the code in compositing/mod.rs was moved around, which makes the commit changes a bit difficult to follow

@metajack

This comment has been minimized.

The comment here is incorrect as create_new_compositor returns nothing.

@metajack

This comment has been minimized.

The name CompositorTask::create_compositor_task seems a little redundant.

@metajack

This comment has been minimized.

Copy link

metajack commented on src/components/main/engine.rs in 496069d Jun 17, 2013

If this is no longer needed, just delete the whole Drop implementation.

bors-servo pushed a commit that referenced this pull request Jun 17, 2013
communicate via layout
refactor channel wrappers from *Task --> *Chan
@metajack
Copy link
Contributor

metajack commented Jun 17, 2013

The rust-glut pointer is bad:

 Unable to checkout '6f6b6fa95914fa6322f3277c803fd4921601cb90' in submodule path 'src/support/glut/rust-glut'
bors-servo pushed a commit that referenced this pull request Jun 17, 2013
communicate via layout
refactor channel wrappers from *Task --> *Chan
bors-servo pushed a commit that referenced this pull request Jun 17, 2013
communicate via layout
refactor channel wrappers from *Task --> *Chan
bors-servo pushed a commit that referenced this pull request Jun 17, 2013
communicate via layout
refactor channel wrappers from *Task --> *Chan
…AttachCompositorMsg added to render_task::Msg

updated to reflect comments
@metajack

This comment has been minimized.

Copy link

metajack commented on 577a410 Jun 17, 2013

r+

@bors-servo

This comment has been minimized.

Copy link
Contributor

bors-servo commented on 577a410 Jun 17, 2013

saw approval from metajack
at tikue@577a410

This comment has been minimized.

Copy link
Contributor

bors-servo replied Jun 17, 2013

merging tkuehn/servo/master = 577a410 into auto

This comment has been minimized.

Copy link
Contributor

bors-servo replied Jun 17, 2013

tkuehn/servo/master = 577a410 merged ok, testing candidate = d61c455

This comment has been minimized.

Copy link
Contributor

bors-servo replied Jun 17, 2013

fast-forwarding master to auto = d61c455

bors-servo pushed a commit that referenced this pull request Jun 17, 2013
communicate via layout
refactor channel wrappers from *Task --> *Chan
@bors-servo bors-servo merged commit 577a410 into servo:master Jun 17, 2013
1 check passed
1 check passed
default all tests passed
ChrisParis pushed a commit to ChrisParis/servo that referenced this pull request Sep 7, 2014
Address review comments on the Performance Timeline tests.
glennw pushed a commit to glennw/servo that referenced this pull request Jan 16, 2017
Support for non-stacking-context scrolling areas

When we encounter a stacking context which scrolls its contents, we
treat it as a special non-stacking-context scrolling area. All
scrolling areas with the same servo scroll root id will be scrolled in
tandem. Later changes will give these fake stacking contexts their own
display item.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/517)
<!-- Reviewable:end -->
@jdm jdm mentioned this pull request Nov 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.