execCommand spec should have IDL for execCommand, queryCommand* and designMode
Open
Nobody has claimed this yet.
execCommand
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
The execCommand spec[1] doesn't have interface defintion for exeCommand and queryCommand*, we should have it like whatwg spec[2]
partial interface Document {
[CEReactions] attribute DOMString designMode;
[CEReactions] boolean execCommand(
DOMString commandId,
optional boolean showUI = false,
optional DOMString value = "");
boolean queryCommandEnabled(DOMString commandId);
boolean queryCommandIndeterm(DOMString commandId);
boolean queryCommandState(DOMString commandId);
boolean queryCommandSupported(DOMString commandId);
DOMString queryCommandValue(DOMString commandId);
}
[1] http://w3c.github.io/editing/execCommand.html
[2] https://html.spec.whatwg.org/multipage/dom.html#the-document-object
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the execCommand specification linked in the issue and compare its Document interface with the referenced WHATWG definition. Add IDL for designMode, execCommand, and the queryCommand* methods as shown, then verify that the published specification includes the complete interface definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100