[svgwg] Issue: Do we really need not to reflect additional enum values in SVG 2 marked as Needs tests

dirkschulze has just labeled an issue for https://github.com/w3c/svgwg as "Needs tests":

== 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.

See https://github.com/w3c/svgwg/issues/424

Received on Thursday, 10 May 2018 20:07:15 UTC