- From: Johannes Wilm <notifications@github.com>
- Date: Mon, 12 Nov 2018 02:50:47 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/editing/issues/184/437836597@github.com>
> execCommand hasn't been updated in a year, according to the below. No, but had these requests related to it over the past year: https://github.com/w3c/editing/issues/179 https://github.com/w3c/editing/issues/175 https://github.com/w3c/editing/issues/172 https://github.com/w3c/editing/issues/164 https://github.com/w3c/input-events/issues/30#issuecomment-436720554 (there could be more). In at least two browsers (Firefox and Chrome) developers are actively working on execCommand in some way and even though you can find me mention that execCommand is not really expected to go anywhere, there are these developers busy trying to fix it in various ways. > You could say it's me and the W3C, in as far as I've been tasked to chair the group and make it more successful (we have a clearly defined success criteria: get specs to Rec). Ok, in that case this sounds a bit like the new public management of hospitals that chaals is referring to. It sounds like the intention is to help advance those specs that are on track. And this I think is a great idea - it has taken way longer than what it should to get the "Input Events" to go through the system and I could have used some assistance in understanding when we needed tests, etc. when I asked for that. But instead we now spend even more time discussing execCommand and I'm sure that once the execCommand spec no longer is there, we will be pressured into adding execCommand-related things to the other specs. That doesn't really seem to be in line with the original intention. Can we maybe change the status from a draft spec to a draft note or something like that so that it doesn't show up in your count? Then you don't have to worry about it any more. But OK. If your mind is set and you not willing to make any changes to your plan, then I guess we'll live with it. Can we at least link to the new locations of the documents on github.com/w3c/editing ? Else this will really turn into chaals, me and others working on editing being turned into the personal assistant of anyone looking for the execCommand spec (and when not finding it in "editing" starting a new one). And then we only spend more time with no added benefits. -- 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-437836597
Received on Monday, 12 November 2018 10:51:09 UTC