Re: [w3c/editing] inputType should be tied to the command names and having that tied to a way of declaring what you support (#110)

# Which execCommand commands?

What do you guys think about these? @ojanvafai @gked @honiong 

## Useful

Looking at the execCommand names, it seems that these would be useful because there is already an established keyboard shortcut: ```bold, italic, copy, cut, paste, redo, undo, underline, justify (center, right, left), superscript, subscript, delete/backspace (various), outdent```.

The following doesn't have an established keyboard shortcut, but one could imagine creating one: ```strikeThrough, indent [1], insertOrderedList [2], insertUnorderedList [2], insertParagraph [3], removeFormat, insertHorizontalRule```.

These apparently have a shortcut, but the corresponding execCommand seem like they wouldn't do what the established shortcut does: ```increaseFontSize, decreaseFontSize```.

## Possibly useful

Some could work if the browser provides a menu for styling, the way Safari does: ```hiliteColor, foreColor, heading```.

## Not very useful

Other commands seem less helpful. I am not sure how a user would want to express these without JS defined menus: ```unlink, createLink, insertImage```.

 Or whether these are things editors should generally do: ```styleWithCSS, useCSS, unlink, backColor, contentReadOnly, enableInlineTableEditing, enableObjectResizing, formatBlock, insertBrOnReturn```. 

[1]  As tab key isn't normally working for this purpose in browsers.
[2]  Probably: Turn current paragraph into first item in a list.
[3] Probably: Turn the block element where the caret is into a paragraph.

---
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/110#issuecomment-215282880