W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2011

[whatwg] Ongoing work on an editing commands (execCommand()) specification

From: Ehsan Akhgari <ehsan@mozilla.com>
Date: Tue, 22 Mar 2011 11:21:05 -0700 (PDT)
Message-ID: <1085925484.23035.1300818065984.JavaMail.root@cm-mail03.mozilla.org>
----- Original Message -----
> From: "Robert O'Callahan" <robert at ocallahan.org>
> To: "Ehsan Akhgari" <ehsan at mozilla.com>
> Cc: "Aryeh Gregor" <Simetrical+w3c at gmail.com>, "whatwg" <whatwg at lists.whatwg.org>, "Ryosuke Niwa" <rniwa at webkit.org>,
> "Ehsan Akhgari" <ehsan.akhgari at gmail.com>, "Hallvord R. M. Steen" <hallvord at opera.com>
> Sent: Monday, March 21, 2011 11:48:41 PM
> Subject: Re: [whatwg] Ongoing work on an editing commands (execCommand()) specification
> On Tue, Mar 22, 2011 at 12:55 PM, Ehsan Akhgari < ehsan at mozilla.com >
> wrote:
> You're proposing to remove something from Gecko and Webkit which has
> been supported for many years (about 8 years for Gecko). We do not
> have the ability to make sure that nobody is relying on this in any of
> the billions of available web sites. Unless you have a very strong
> argument on why we should remove support for an API as old as this
> one, I'm not sure that we're going to do that, and I think that Webkit
> might have similar constraints as well. So far, the argument that
> you've proposed is extrapolating the assumption that this API doesn't
> have any users from three implementations which use the editing APIs.
> I'm afraid you should have a _much_ larger sample if you want to draw
> this conclusion.
> I would personally very much like to get one of the two modes killed
> in favor of the other, since that means an easier spec to implement,
> less code to maintain, and easier life for me. But I think we should
> carefully think about what this would means for potential users who
> are using the CSS mode in their applications.
> We can deprecate the CSS mode and leave it unspecified, without
> removing it from Webkit and Gecko. That won't hurt interop since
> anyone using it is probably UA-sniffing already.
> If sometime in the future we decide that a "CSS mode" is worth having,
> then someone can start writing a spec for it then.

Yes, that would make sense, I think.

Ehsan Akhgari
ehsan at mozilla.com
Received on Tuesday, 22 March 2011 11:21:05 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC