aboutsummaryrefslogtreecommitdiffstats
path: root/components/script/page.rs
diff options
context:
space:
mode:
authorPatrick Walton <pcwalton@mimiga.net>2014-09-30 13:19:39 -0700
committerPatrick Walton <pcwalton@mimiga.net>2014-10-01 18:34:53 -0700
commit287fe3b3aba157ac7e9dbe5da4433ef256745549 (patch)
tree086d0d7a93efadf3dcfc123fca0c8471178ca7b2 /components/script/page.rs
parentf80096069592b864221abe112eaf2ecb6c444fda (diff)
downloadservo-287fe3b3aba157ac7e9dbe5da4433ef256745549.tar.gz
servo-287fe3b3aba157ac7e9dbe5da4433ef256745549.zip
layout: Implement the correct hypothetical box behavior for
absolutely-positioned elements declared with `display: inline`. Although the computed `display` property of elements with `position: absolute` is `block`, `position: absolute; display: inline` can still behave differently from `position: absolute; display: block`. This is because the hypothetical box for `position: absolute` can be at the position it would have been if it had `display: inline`. CSS 2.1 § 10.3.7 describes this case in a parenthetical: "The static-position containing block is the containing block of a hypothetical box that would have been the first box of the element if its specified 'position' value had been 'static' and its specified 'float' had been 'none'. (Note that due to the rules in section 9.7 this hypothetical calculation might require also assuming a different computed value for 'display'.)" To handle this, I had to change both style computation and layout. For the former, I added an internal property `-servo-display-for-hypothetical-box`, which stores the `display` value supplied by the author, before the computed value is calculated. Flow construction now uses this value. As for layout, implementing the proper behavior is tricky because the position of an inline fragment in the inline direction cannot be determined until height assignment, which is a parallelism hazard because in parallel layout widths are computed before heights. However, in this particular case we can avoid the parallelism hazard because the inline direction of a hypothetical box only affects the layout if an absolutely-positioned element is unconstrained in the inline direction. Therefore, we can just lay out such absolutely-positioned elements with a bogus inline position and fix it up once the true inline position of the hypothetical box is computed. The name for this fix-up process is "late computation of inline position" (and the corresponding fix-up for the block position is called "late computation of block position"). This improves the header on /r/rust.
Diffstat (limited to 'components/script/page.rs')
0 files changed, 0 insertions, 0 deletions