On Tue, May 13, 2014 at 11:26 AM, Dirk Schulze <dschu...@adobe.com> wrote:
> contentEditable can be fairly useful in SVG as well. It partly works for 
> inline SVG content in web browsers today.
> The question is, should SVGElement add support for 
> contentEditable/isContentEditable and add it to its interface? Or should both 
> attributes move to the Element interface instead?

I suggest we wait with deciding upon this until browsers have moved
id/class support to Element as per the DOM Standard. Seems best to
make some incremental steps here to see what problems we run into.


Reply via email to