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

Fix current_dom_depth in sequential traversal. (fixes #14414) #14459

Merged
merged 1 commit into from Dec 5, 2016

Conversation

@heycam
Copy link
Member

heycam commented Dec 5, 2016

Since we pass around a reference to the one PerLevelTraversalData object in sequential traversal, we must update it after we process children. Alternatively, we could switch to what the parallel traversal is doing and clone the object when passing it down.

r? @emilio


  • ./mach build -d does not report any errors
  • ./mach test-tidy does not report any errors
  • These changes fix #14414 (github issue number if applicable).
  • There are tests for these changes OR
  • These changes do not require tests because _____

This change is Reviewable

@highfive
Copy link

highfive commented Dec 5, 2016

Heads up! This PR modifies the following files:

  • @bholley: components/style/sequential.rs
  • @emilio: components/style/sequential.rs
@highfive
Copy link

highfive commented Dec 5, 2016

warning Warning warning

  • These commits modify style code, but no tests are modified. Please consider adding a test!
@emilio
Copy link
Member

emilio commented Dec 5, 2016

Oh, of course...

@bors-servo r+

@bors-servo
Copy link
Contributor

bors-servo commented Dec 5, 2016

📌 Commit 78c8128 has been approved by emilio

@bors-servo
Copy link
Contributor

bors-servo commented Dec 5, 2016

Testing commit 78c8128 with merge c2515f9...

bors-servo added a commit that referenced this pull request Dec 5, 2016
Fix current_dom_depth in sequential traversal. (fixes #14414)

<!-- Please describe your changes on the following line: -->

Since we pass around a reference to the one `PerLevelTraversalData` object in sequential traversal, we must update it after we process children.  Alternatively, we could switch to what the parallel traversal is doing and clone the object when passing it down.

r? @emilio

---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [X] These changes fix #14414 (github issue number if applicable).

<!-- Either: -->
- [ ] There are tests for these changes OR
- [ ] These changes do not require tests because _____

<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/14459)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Dec 5, 2016

@bors-servo bors-servo merged commit 78c8128 into servo:master Dec 5, 2016
3 checks passed
3 checks passed
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
homu Test successful
Details
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.

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