Re: [svgwg] Add advice on how to handle className conflict in DOM?

What I'd *like* to do is to have SVGElement.className act as a regular
 DOM string that has special properties `.animVal` and `.baseVal` that
 implement the old SVGAnimatedString behavior.  See 
https://github.com/w3c/svgwg/issues/175 for my musings about speccing 
that sort of behavior SVG-wide.

In the short term, however, based on existing implementations, the 
guidance is more that "the `.className` property of SVGElement 
*overrides* the property of the same name on the `Element` interface".

Of course, whether this is easy or hard to implement depends on the 
type-strictness of the language in which you're implementing the DOM.

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

Received on Thursday, 8 December 2016 01:01:59 UTC