- From: Aryeh Gregor <ayg@aryeh.name>
- Date: Tue, 1 May 2012 08:41:45 +0300
On Mon, Apr 30, 2012 at 5:35 PM, David Young <dyoung at pobox.com> wrote:
> I have seen this spec before. ?It seems to have something to do
> with creating a word processor-like environment in the browser,
> something that I am acutely interested in, but there isn't much
> introduction/justification to it. ?Is there an executive summary of the
> editing API somewhere?
I filed a bug to remind me to add a better intro at some point, but no
guarantees that I'll get to it in the foreseeable future:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16894
You can read tutorials and such that you can find by Googling
"contenteditable" or "execCommand". This page looks especially good,
at a glance, like most things written by Mark Pilgrim:
http://blog.whatwg.org/the-road-to-html-5-contenteditable
On Tue, May 1, 2012 at 1:03 AM, Ojan Vafai <ojan at chromium.org> wrote:
> This looks good to me. Could we just call the method setText though since
> the range values are optional. setRangeText, in retrospect, is wordy and
> confusing in a way that setText isn't IMO.
.setText("foo") sounds like it should set the entire text, not just
the selected text.
Received on Monday, 30 April 2012 22:41:45 UTC