- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Apr 2019 05:18:49 +0000
- To: public-svg-issues@w3.org
Proposal was to
* support the following presentation attributes/CSS properties:
* `clip-path`
* `clip-rule`
* `color`
* `display` (values other than `none` ignored)
* `fill`
* `fill-opacity`
* `fill-rule`
* `opacity`
* `stroke`
* `stroke-dasharray`
* `stroke-dashoffset`
* `stroke-linecap`
* `stroke-linejoin`
* `stroke-miterlimit`
* `stroke-opacity`
* `stroke-width`
* `stop-color`
* `stop-opacity`
* `visibility` (values other than `visible`, `hidden` ignored)
* support the [`style` attribute](https://www.w3.org/TR/SVG2/styling.html#ElementSpecificStyling) with its declaration list.
* **No support** for `<style>` (and therefore) media queries, any @-rules, selectors or combinators
* Property inheritance stays.
* Values and units have the following restrictions
* Pre-defined keywords (`inherit`, `unset`, `reset`,...), important declarations get ignored.
* Only absolute length units or percentage.
* functional notations limited to: `url()`, `rgb()` (and possibly `var()` with limitations... other issue). **No** `calc()`, `att()`, `image()`, `rgba()`, ... .
* Color values other than color keywords (but system colors), `rgb()`, hex (3-6 digits) and `var()` (with strict limitations) get ignored.
* Support of `currentColor` for `fill`, `stroke`, `stroke-color`.
--
GitHub Notification of comment by dirkschulze
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/658#issuecomment-483514774 using your GitHub account
Received on Tuesday, 16 April 2019 05:23:52 UTC