- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sat, 05 Nov 2016 01:40:56 +0000
- To: public-fxtf-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion] CSS and SVG box correspondence seems overly-simplistic == > For SVG elements without associated CSS layout box, the used value for content-box, padding-box, border-box and margin-box is fill-box. > > For elements with associated CSS layout box, the used value for fill-box, stroke-box and view-box is border-box. The [Paint module](https://drafts.fxtf.org/paint/#fill-origin) uses a bit more sophistication in its box mappings: content-box | padding-box -> fill-box and border-box -> stroke-box. (The mapping in the other direction relates to text bounds, which is maybe not appropriate here.) At the very least, these two modules should be consistent in how they map the SVG and CSS terms where possible. Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/66 using your GitHub account
Received on Saturday, 5 November 2016 01:41:02 UTC