- From: Johannes Wilm <notifications@github.com>
- Date: Tue, 13 Nov 2018 09:34:29 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 13 November 2018 17:34:50 UTC
I disagree that "It will enable more input from the developer community" to move it to WICG. If it's burried among 300+ other groups on other things and no longer with the rest of the editing-related documents it will likely mean less input from developers. And there is a good chance we will get just as many execCommand-related issues filed in the editing taskforce with the difference that those issues will ask for adding execCommand-related features to the other documents we have there. Already now a fair amount of issues filed there from people who have not attended Editing Taskforce meetings are related to execCommand in some way or other even though they can see that the execCommand spec has a huge note saying that this is not really the way to move forward. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/185#issuecomment-438364346
Received on Tuesday, 13 November 2018 17:34:50 UTC