[fxtf-drafts] [motion] contain should modify percentages, not path

fantasai has just created a new issue for 
https://github.com/w3c/fxtf-drafts:

== [motion] contain should modify percentages, not path ==
> contain
>   When the absolute value of offset-distance would select a point on
 the path which is outside the edge of the containing element, the 
value is instead clipped so that the selected point lies on the edge 
of the element. 

The `contain` value would make a lot more sense if, instead of 
clipping the `offset-distance`, it merely altered the interpretation 
of percentages so that 100% placed the element wholly inside its 
containing block. IIRC this was the original reason for placing it as 
part of the `offset-path` property rather than `offset-distance`: it 
operates by altering the length of the path, not by altering the 
distance along it. This will make percentages interpolate much more 
reasonably than the currently specified model.

Please view or discuss this issue at 
https://github.com/w3c/fxtf-drafts/issues/61 using your GitHub account

Received on Saturday, 5 November 2016 01:01:27 UTC