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

[motion] Note about closest-side seems wrong #62

Closed
fantasai opened this issue Nov 5, 2016 · 0 comments
Closed

[motion] Note about closest-side seems wrong #62

fantasai opened this issue Nov 5, 2016 · 0 comments
Labels

Comments

@fantasai
Copy link
Contributor

fantasai commented Nov 5, 2016

Note: When the initial position is at one of the corners of the containing block, the closest side takes the edge that the initial position is on. Even if the offset given by <length> or <percentage> changes, the position of the element specified with closest-side is the same.

This seems wrong. If the initial position is at the corner and closest-side is specified, then a percentage offset-distance will be zero, because the path is zero-length. But since it is defined as an unbounded ray, a distance should move in the specified direction.

ewilligers pushed a commit to ewilligers/fxtf-drafts that referenced this issue Nov 14, 2016
If the initial position is on an edge, the path is zero length.

Resolves w3c#62
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant