Revision 2d080f1a7dd986dcd3f33a7676d30f367217d988 authored by Eric Willigers on 03 October 2017, 02:21:05 UTC, committed by Chromium WPT Sync on 03 October 2017, 02:21:05 UTC
When offset-position is not 'auto', the path begins at offset-position. When offset-position is not 'auto', but offset-path is 'none', we have a simple translation to offset-position. In this case, offset-anchor uses the same value as offset-position, but with percentages referring to the element's width/height and not the containing block's width/height. Spec: https://drafts.fxtf.org/motion-1/#offset-position-property https://drafts.fxtf.org/motion-1/#offset-anchor-property Work remaining: For this initial implementation, we use the parent layout object instead of the true containing block. (When an element is absolutely positioned and the parent element is the containing block, these are the same.) BUG=638055 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I53e5b576adebf65ede8ebd1dabe084713ebdf875
1 parent 85a1716
| File | Mode | Size |
|---|---|---|
| Gyroscope.https.html | -rw-r--r-- | 435 bytes |
| Gyroscope_insecure_context.html | -rw-r--r-- | 574 bytes |
| Gyroscope_onerror-manual.https.html | -rw-r--r-- | 577 bytes |
| OWNERS | -rw-r--r-- | 63 bytes |
| idlharness.https.html | -rw-r--r-- | 1.6 KB |
Computing file changes ...
