- From: Boris Chiou via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Sep 2019 20:15:55 +0000
- To: public-fxtf-archive@w3.org
BorisChiou has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion-1] The definition of "containing box" for ray() function == The definition of [`<size>`](https://drafts.fxtf.org/motion-1/#valdef-offsetpath-size) in [`ray()`](https://drafts.fxtf.org/motion-1/#valdef-offsetpath-ray) is: > Decides the path length used when offset-distance is expressed as a percentage, using the distance to the containing box. I guess this is pretty similar to [`containing block`](https://drafts.csswg.org/css2/visudet.html#containing-block-details), right? So should we choose a different edge based on `position` property? Or just always use border edge or padding edge? It seems always using padding edge may make sense becuase it looks like `contain` flag doesn't expect the element overlaps the borders, but I'm not sure. If the element is an SVG element (e.g. `<rect>`), how do we define this containing box on SVG layout? Perhaps we need a better definition for this. Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/369 using your GitHub account
Received on Friday, 6 September 2019 20:15:56 UTC