The HTML Editing APIs has been proposed:<\/p>\n
A group to work on APIs and other functionality related to rich-text HTML editing, such as:<\/p>\n
* The contenteditable and designMode attributes
\n* The execCommand(), queryCommandEnabled(), queryCommandIndeterm(), queryCommandState(), queryCommandSupported(), and queryCommandValue() methods on the Document interface
\n* What exact effect user actions (such as typing text or hitting Enter) should have on rich-text editable regions
\n* The Selection interface
\n* Spellcheck for rich-text editable regions
\n* Other functionality related to the foregoing<\/p>\n
The group is expected to work on writing high-quality, detailed technical specifications suited for implementation by major browsers. It will start work with the preliminary specification hosted at <http:\/\/aryeh.name\/spec\/editing\/editing.html>, and later add the Selection part of <http:\/\/html5.org\/specs\/dom-range.html>, both of which are currently developed entirely outside the W3C and are not close to interoperable implementation. The group’s deliverables are expected to be submitted to the Recommendation track in the WebApps WG after they mature sufficiently.<\/p>\n
You are invited to support the creation of this group<\/a>. Once the group has a total of five supporters, W3C launch the group and people can join to begin work.<\/p>\n In order to join the group, you will need a W3C account<\/a>.<\/p>\n If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on site-comments@w3.org<\/a><\/p>\n Thank you, The HTML Editing APIs has been proposed: A group to work on APIs and other functionality related to rich-text HTML editing, such as: * The contenteditable and designMode attributes * The execCommand(), queryCommandEnabled(), queryCommandIndeterm(), queryCommandState(), queryCommandSupported(), and queryCommandValue() methods on … Continue reading
\nW3C Community Development Team<\/p>\n","protected":false},"excerpt":{"rendered":"