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

Remove overscroll code and api. #2629

Merged
merged 1 commit into from
Apr 6, 2018
Merged

Conversation

glennw
Copy link
Member

@glennw glennw commented Apr 6, 2018

Fixes #2545.
Fixes #1762.
Fixes #1314.


This change is Reviewable

@glennw glennw requested a review from mrobinson April 6, 2018 05:26
@glennw
Copy link
Member Author

glennw commented Apr 6, 2018

This is better handled at a higher level by the embedder / client, as per #2545.

I'm not sure if I removed too much - I wasn't quite sure if we still need the ScrollEventPhase?

Long term, we should probably switch Servo to use the API that Gecko uses to scroll by a specific scroll node, and remove the other scroll API, I think?

r? @mrobinson

@mrobinson
Copy link
Member

@bors-servo r+

@bors-servo
Copy link
Contributor

📌 Commit c262d18 has been approved by mrobinson

@bors-servo
Copy link
Contributor

⌛ Testing commit c262d18 with merge a05186d...

bors-servo pushed a commit that referenced this pull request Apr 6, 2018
Remove overscroll code and api.

Fixes #2545.
Fixes #1762.
Fixes #1314.

<!-- 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/2629)
<!-- Reviewable:end -->
@mrobinson
Copy link
Member

I wonder if we can also remove DisplayListFlattener::setup_viewport_offset and related API as well.

@bors-servo
Copy link
Contributor

☀️ Test successful - status-appveyor, status-taskcluster
Approved by: mrobinson
Pushing a05186d to master...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants