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>
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