- From: Robert Longson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Apr 2018 07:20:59 +0000
- To: public-svg-issues@w3.org
longsonr has just created a new issue for https://github.com/w3c/svgwg: == Do we really need not to reflect additional enum values in SVG 2 == Looks like Firefox forgot to do this in bug https://wpt.fyi/svg/types/scripted/SVGAnimatedEnumeration-SVGFEBlendElement.html although it does not expose the additional values. Nobody seems to have noticed except me. Implementers have to record any new values for enums somewhere so we need to write logic along the lines of if the enum value is > the maximum SVG 1.1 value and someone calls baseValue or animValue return 0. Then we need some kind of baseValueInternal implementation so we can work with the real value internally. Why not just add the new values to the webidl and reflect everything? It's simpler to implement. There's not that many changes, feBlend's additional modes, marker auto-start-reverse and feComposite's operator. Please view or discuss this issue at https://github.com/w3c/svgwg/issues/424 using your GitHub account
Received on Monday, 23 April 2018 07:21:03 UTC