Re: [w3c/editing] `Document.execCommand`, `Document.queryCommandValue`, `Document.queryCommandState`, `Document.queryCommandEnabled`, `Document.queryCommandSupported`, `Document.queryCommandIndeterm` behavior when an EditContext editing host has focus (Issue #447) from Johannes Wilm on 2023-10-13 (public-webapps-github@w3.org from October 2023)

From: Johannes Wilm <notifications@github.com>
Date: Fri, 13 Oct 2023 01:08:48 -0700
To: w3c/editing <editing@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/editing/issues/447/1761088910@github.com>

It is possible that in five years time, `contenteditable` usage will have been replaced entirely by edit context and new developers will not know what `execCommand` even is. Then it would be the best if everything related to execCommand is in the `execCommand` spec and not everywhere else. 

In order to not litter `execCommand` in every new spec, would it be possible to put this into the execCommand spec itself instead?

CC: @zcorpan 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/447#issuecomment-1761088910
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/447/1761088910@github.com>

Received on Friday, 13 October 2023 08:08:53 UTC