- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 May 2019 20:59:20 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `Which CSS concepts should be supported in presentation attributes?`, and agreed to the following: * `RESOLUTION: SVG Native requires env()` <details><summary>The full IRC log of that discussion</summary> <krit> topic: Which CSS concepts should be supported in presentation attributes?<br> <krit> GitHub: https://github.com/w3c/svgwg/issues/681<br> <krit> myles: Made a proposal as a starting point<br> <krit> myles: We resolved that we need var() last time. env() is a better fit and we will use it eventually.<br> <krit> AmeliaBR: the spec was not stable and when adopted it should be treated as var(). Maybe some text like that.<br> <krit> myles: percentages are not difficult to implement but not sure what it would be used for. lets do relative units first...<br> <krit> myles: Relative units doesn't fit the requirement that there is just one layout and the layout should not change dependent on the content it lives in (similar to PNG)<br> <krit> AmeliaBR: we might want to have special rules for outside SVG (or maybe not?). Maybe it makes sense to always have absolute values on SVG root?<br> <krit> myles: Presumably an image element would be styled with a width and height already<br> <krit> AmeliaBR: just an intrinsic width and height<br> <krit> AmeliaBR: benefits for abs values is forcing an absolute/explict intrinsic dimension.<br> <krit> myles: I think I agree on that. Good argument for abs values even on SVG root.<br> <krit> AmeliaBR: then we have viewBox requirement on SVG root element.<br> <krit> AmeliaBR: if there is none, then percentages make a difference depending on the computed viewport.<br> <krit> AmeliaBR: spect ratio is special and separate from rel/abs units.<br> <krit> myles: If you create a native apps and you put in some things inside it and change the size the resource it might be very unexpected.<br> <krit> AmeliaBR: viewBox can be discussed separately.<br> <krit> myles: Requiring env() is future proof and if it works as var() not difficult?<br> <krit> myles: "If you support var() you should support env()"<br> <krit> myles: since var is required, env is required.<br> <krit> RESOLUTION: SVG Native requires env()<br> <krit> trackbot, end telcon<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/681#issuecomment-494148939 using your GitHub account
Received on Monday, 20 May 2019 20:59:22 UTC