diff options
author | bors-servo <metajack+bors@gmail.com> | 2015-08-17 13:56:53 -0600 |
---|---|---|
committer | bors-servo <metajack+bors@gmail.com> | 2015-08-17 13:56:53 -0600 |
commit | d654841288ad6c7d4f8d7da3c68d04ef7df2c241 (patch) | |
tree | e0b6e3e13b89ae5b936af6a8511d2110be75af6b /components/net/resource_task.rs | |
parent | 72fa45155b93a9763967cf215e3a9e60e3883cd9 (diff) | |
parent | a30379975a50e52dd8ad7b7b0f95447efe231c5a (diff) | |
download | servo-d654841288ad6c7d4f8d7da3c68d04ef7df2c241.tar.gz servo-d654841288ad6c7d4f8d7da3c68d04ef7df2c241.zip |
Auto merge of #7177 - pcwalton:intervening-inline-block, r=mbrubeck
layout: Improve our handling of inline absolute containing blocks.
Several issues are addressed in this commit:
* Inline flows now bubble up their absolute descendants instead of
making the inline flow the containing block for them. (In the future,
we will need to make the inline flow *sometimes* be the containing
block for them, but for now it improves sites to unconditionally
bubble up.)
* Fragments now look at their inline fragment context to determine
whether they are positioned.
* Inline flows now push the stacking-relative position of the absolute
containing block down to their inline-block fragments.
* Inline absolute hypothetical fragments can be containing blocks.
* Fixes the logic in
`containing_block_range_for_flow_surrounding_fragment_at_index`. The
condition to determine whether fragments are positioned was inverted!
* `Descendants`/`AbsDescendants` has been refactored in order to become
more friendly to inline absolute containing blocks in the future.
Improves the inline position of the green drop-down arrow in the Google
SERPs. (The block position is still wrong.)
r? @mbrubeck
<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/7177)
<!-- Reviewable:end -->
Diffstat (limited to 'components/net/resource_task.rs')
0 files changed, 0 insertions, 0 deletions