W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2014

RE: [Editing] Tracking Issues in GitHub

From: Ben Peters <Ben.Peters@microsoft.com>
Date: Mon, 6 Oct 2014 20:29:56 +0000
To: Piotr Koszuliński <p.koszulinski@cksource.com>
CC: "public-editing-tf@w3.org" <public-editing-tf@w3.org>, "public-indie-ui@w3.org" <public-indie-ui@w3.org>, public-webapps <public-webapps@w3.org>
Message-ID: <c710ea2dd3d24b42b618f9657d564005@BLUPR03MB437.namprd03.prod.outlook.com>
Yes, that would be great!!

From: Piotr Koszuliński [mailto:p.koszulinski@cksource.com]
Sent: Wednesday, October 1, 2014 5:20 AM
To: Ben Peters
Cc: public-editing-tf@w3.org; public-indie-ui@w3.org; public-webapps
Subject: Re: [Editing] Tracking Issues in GitHub

Hey,

On the Extensible Web Summit in Berlin we talked about creating a list of problems which we have with contenteditable, or more generally - when implementing editors. I started writing stuff down for such list. I've got things like what to do with bogus <br>s (aka extraneous line breaks) or typing spaces at the end of blocks, standard way for getting range from point or even about nightmarish HTML in the clipboard. Do you think that this GitHub issues page is the right place for them?

On Tue, Sep 23, 2014 at 2:40 AM, Ben Peters <Ben.Peters@microsoft.com<mailto:Ben.Peters@microsoft.com>> wrote:
In order to simplify and streamline communication on open issues for Editing and Intentions, I suggest we have more conversations on GitHub. To that end, I have opened Issues for the list of bugs in the spec, and removed them from the spec itself. If there are no objections, please check out our GitHub Issues page [1] to open new issues and comment on existing issues.

Ben

[1] https://github.com/w3c/editing-explainer/issues





--
Piotrek Koszuliński
CKEditor JavaScript Lead Developer
Received on Monday, 6 October 2014 20:30:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:31 UTC