- From: Eric Willigers via GitHub <sysbot+gh@w3.org>
- Date: Sun, 25 Nov 2018 08:10:08 +0000
- To: public-svg-issues@w3.org
ewilligers has just submitted a new pull request for https://github.com/w3c/svgwg: == stop-opacity computed value is clamped == Like other *-opacity properties, the computed value for stop-opacity is clamped to [0,1]. stop-opacity is currently the only one of the following properties not to have this clamping mentioned in "Computed value:" wording. - [opacity](https://drafts.csswg.org/css-color/#propdef-opacity) - [flood-opacity](https://drafts.fxtf.org/filter-effects/#FloodOpacityProperty) - [fill-opacity](https://drafts.fxtf.org/fill-stroke/#fill-opacity) (also in [SVG2](https://svgwg.org/svg2-draft/painting.html#FillOpacity)) - [stroke-opacity](https://drafts.fxtf.org/fill-stroke/#stroke-opacity) (also in [SVG2](https://svgwg.org/svg2-draft/painting.html#StrokeOpacity)) - stop-opacity (in [SVG2](https://svgwg.org/svg2-draft/pservers.html#StopOpacityProperty)) See https://github.com/w3c/svgwg/pull/601
Received on Sunday, 25 November 2018 08:10:11 UTC