Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible

#315 should be https://github.com/w3c/svgwg/pull/409 (we agreed to change target to DOMString due to low usage)

#312 is a HTML change and I'll work with them to do that (it is the same issue as moving the members into a shared mixin that would make the above change obsolete)

I'll do another PR to add putForwards/stringifier. I can also implement in Edge. PutForward generates all the code needed automatically so that is a trivial change. stringifier should be straightforward too. At least on baseVal. If we want to add on SVGAElement (probably in href's mixin) to match HTMLAElement.toString() behaviour of returning the href string, then that will need a custom specified stringifier. I believe you do that in WebIDL by specifying  new member stringifier and defining the behaviour in prose.

-- 
GitHub Notification of comment by dstorey
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/175#issuecomment-382005348 using your GitHub account

Received on Tuesday, 17 April 2018 14:07:02 UTC