- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Aug 2018 21:53:33 +0000
- To: public-css-archive@w3.org
> The `<foreignObject>` still doesn't, it just provides an ICB to the contained `<html>` element, which does generate a box. You can't have an `<html>` or `<body>` inside a `<foreignObject>` in inline SVG parsed by the HTML parser. Ideally, the foreignObject would provide a fixed-height containing block (most browsers do _not_ currently treat it as if it had a fixed height, so you can't set `height: 100%` on a child) for all child CSS boxes, but I'm not sure whether it is necessary to define it as a CSS box. Basically, a `foreignObject` is a CSS box in the sense of having an inner display type (flow-root), but it does not have an outer display type. More generally, see @tabatkins's [comment on the filter / containing block issue](https://github.com/w3c/fxtf-drafts/issues/307#issuecomment-410373975): > The proper resolution to this boils down to "actually define how SVG operates in the CSS box model finally", correct? -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2987#issuecomment-410385899 using your GitHub account
Received on Friday, 3 August 2018 21:53:41 UTC