Re: [whatwg] Move contentEditable/isContentEditable from HTMLElement to Element? from Anne van Kesteren on 2014-05-13 (public-whatwg-archive@w3.org from May 2014)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 13 May 2014 11:33:51 +0200
To: Dirk Schulze <dschulze@adobe.com>
Cc: whatwg <whatwg@lists.whatwg.org>
Message-ID: <CADnb78g8qi7kFD5mPYMQaSP7gNA=3cMaC9_9=Pn-aa-XcC18eg@mail.gmail.com>

On Tue, May 13, 2014 at 11:26 AM, Dirk Schulze <dschulze@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.

-- 
http://annevankesteren.nl/

Received on Tuesday, 13 May 2014 09:34:15 UTC