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

Avoid a panic when handling collapsing borders (fixes #7144) #7243

Merged
merged 1 commit into from Aug 18, 2015

Conversation

@nox
Copy link
Member

nox commented Aug 16, 2015

There is no need to compute next_collapsed_borders_in_block_direction for all kind of flows when it's used only in the table row case. That also avoids a panic when the next child is a table colgroup (this should not happen when iterating over a table row).

Review on Reviewable

@pcwalton
Copy link
Contributor

pcwalton commented Aug 17, 2015

@bors-servo
Copy link
Contributor

bors-servo commented Aug 17, 2015

📌 Commit bb204ea has been approved by pcwalton

@bors-servo
Copy link
Contributor

bors-servo commented Aug 18, 2015

Testing commit bb204ea with merge 2bcef80...

bors-servo pushed a commit that referenced this pull request Aug 18, 2015
Avoid a panic when handling collapsing borders (fixes #7144)

There is no need to compute next_collapsed_borders_in_block_direction for all kind of flows when it's used only in the table row case. That also avoids a panic when the next child is a table colgroup (this should not happen when iterating over a table row).

<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/7243)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Aug 18, 2015

💔 Test failed - linux2

There is no need to compute next_collapsed_borders_in_block_direction for all
kind of flows when it's used only in the table row case. That also avoids a panic
when the next child is a table colgroup (this should not happen when iterating
over a table row).
@nox nox force-pushed the nox:border-collapse-panic branch from bb204ea to d885958 Aug 18, 2015
@nox
Copy link
Member Author

nox commented Aug 18, 2015

@bors-servo r=pcwalton

I just updated the CSS expectations, didn't notice that there are more passing tests now. :)

@bors-servo
Copy link
Contributor

bors-servo commented Aug 18, 2015

📌 Commit d885958 has been approved by pcwalton

@bors-servo
Copy link
Contributor

bors-servo commented Aug 18, 2015

Testing commit d885958 with merge 3d0951c...

bors-servo pushed a commit that referenced this pull request Aug 18, 2015
Avoid a panic when handling collapsing borders (fixes #7144)

There is no need to compute next_collapsed_borders_in_block_direction for all kind of flows when it's used only in the table row case. That also avoids a panic when the next child is a table colgroup (this should not happen when iterating over a table row).

<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/7243)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Aug 18, 2015

☀️ Test successful - android, gonk, linux1, linux2, mac1, mac2, mac3

@bors-servo bors-servo merged commit d885958 into servo:master Aug 18, 2015
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
homu Test successful
Details
@nox nox deleted the nox:border-collapse-panic branch Aug 20, 2015
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

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