- From: Philip Rogers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2020 16:43:46 +0000
- To: public-svg-issues@w3.org
When implementing resize-observer in chromium, we found an issue related to this where the resize-observer and box-model definitions to not agree. Should "content-box" use the fill-box for SVG and "border-box" use the stroke-box for SVG? The [resize-observer](https://drafts.csswg.org/resize-observer/#calculate-box-size) spec states that: ``` If target is an SVGGraphicsElement Set computedSize.inlineSize to target’s bounding box inline length. Set computedSize.blockSize to target’s bounding box block length. If target is not an SVGGraphicsElement If observedBox is "border-box" Set computedSize.inlineSize to target’s border area inline length. Set computedSize.blockSize to target’s border area block length. If observedBox is "content-box" Set computedSize.inlineSize to target’s content area inline length. Set computedSize.blockSize to target’s content area block length. ``` The [css-box](https://drafts.csswg.org/css-box-3/#keywords) spec states: ``` content-box Refers to the content box or content edge. (In an SVG context, treated as fill-box.) ... border-box Refers to the border box or border edge. (In an SVG context, treated as stroke-box.) ``` -- GitHub Notification of comment by progers Please view or discuss this issue at https://github.com/w3c/svgwg/issues/713#issuecomment-580344183 using your GitHub account
Received on Thursday, 30 January 2020 16:43:48 UTC