Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185)

I disagree with the proposal.

If W3C is getting some type of funding based on ratio of specs reaching recs or similar, I support making changes to draft statuses, etc. if it means that there is no perceivable difference to the JS and browser developers, they can find all the documents in the same place and we only have to consider one email list and one meeting to deal with everything editing-related.

As far as I have come to understand though, this is not the case and it will only make life more difficult for those trying to solve the complex issue of fixing text editing on the web with all the aspects that come with it. JS editors currently have to execute at least two execCommands (on Firefox) and possible 1-2 more in other situations and the rest of the time they deal with other editing related APIs. They don't care in which spec things are - they just need to get it done with at least one of them. Sending them to different meetings to discuss basically the same thing and hope that at least one of the groups comes up with a usable API that is being implemented bugfree for each particular operation they hope to achieve (make bold, enter some text, cut something, enter an image, etc.) is likely to set back the progress we have achieved in this area over the past four years.

I also 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. 

You may or may not be aware of me having contacted all JS editing projects we have been able to identify and collect opinions from them on a number of issues as well as invite them to join the mailing list and comment on github.

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 (in our opinion).

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