Re: [w3c/editing] Move execCommand to WICG (#184)

I would also think it is fine to move it to WICG and I agree with others here that I don't see this being standardized in browsers.

That being said, I do think it's important we continue to be able to edit it because we continue to get requests that are linked to execCommand in some way. For example juts a few days ago, from Firefox we basically had a request to add a number of inputTypes to the beforeinput/input events spec that are only available through execCommand. There are clearly some parts of the browser world who have not given up on execCommand (and history has shown that sometimes they can be right in not giving up on some features that are believed to be dead), and I would prefer to keep such execCommand extras in an execCommand draft spec rather than add execCommand-related things into all the new specs we are writing.

However if it is an organizational issue for the W3C that the Editing taskforce needs to only produce production level specs, maybe we can solve this by simply making all members of the editing taskforce also members of this newly created WICG so that we can then edit the execCommand drfat spec if need be without having to make a separate meeting or a second group for that?

> I don't see why. The Working Group's goal, even more than "produce Recommendations" is "do useful work in its scope", and a bureaucratic shuffle merely to keep our specs -> Recs tally looking good reminds me more of a super-efficient fictional hospital (see Yes, Minister) than a functional approach to the work we try to do.

If chaals is right that there is not such a hard requirement of producing specs (and we will not move any faster with the other specs because the execCommand spec is now stored somewhere else), then I agree that it doesn't make sense to move it just yet. 



-- 
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/184#issuecomment-437662883