CSS Motion Path: begin path at offset-position #7362
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wpt-pr-bot
approved these changes
Sep 16, 2017
Build PASSEDStarted: 2017-10-03 02:21:56 Failing Jobs
View more information about this build on: |
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-I53e5b576adebf65ede8ebd1dabe084713ebdf875
branch
2 times, most recently
from
08baf27
to
f441a8b
Compare
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-I53e5b576adebf65ede8ebd1dabe084713ebdf875
branch
from
f441a8b
to
81f67f2
Compare
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
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-I53e5b576adebf65ede8ebd1dabe084713ebdf875
branch
from
81f67f2
to
2d080f1
Compare
|
Close this PR because thi is a Stale chromium-export PR/branche. |
KyleJu
deleted the
chromium-export-cl-I53e5b576adebf65ede8ebd1dabe084713ebdf875
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Reviewed-on: https://chromium-review.googlesource.com/666945
WPT-Export-Revision: bac07975d1f07ff9ea4bf334bfb507fcb4989bc0