diff --git a/CHARTER.md b/CHARTER.md new file mode 100644 index 0000000..48e3fe1 --- /dev/null +++ b/CHARTER.md @@ -0,0 +1,70 @@ + +**Confidentiality:** Proceedings are [public](https://www.w3.org/2005/10/Process-20051014/comm.html#confidentiality-levels)  + +**Chairs(acting as delegates from the WebApps WG chairs):** Johannes Wilm (Invited Expert), Grisha Lyukshin (Microsoft) + +**Meeting Schedules:** Teleconferences: On an as-needed basis. Preferably, a minimum of one status meeting per month. Face-to-face meetings: On an as-needed basis. Video Conferences: On an as-needed basis.  + +### Abstract + +Enabling rich editing experience on the web is currently a challenging task. Reasons are many. For example, lack of requirements in the behavior of the `contenteditable` attribute in HTML, currently, the only browser primitive providing rich editing surface to web developers. Also, lack of support for low level editing APIs that would allow web developers to build rich editing experiences without getting browsers interference in this process. + +Editing Task Force sets out to explore limitations in existing browser primitives, provide use cases for new APIs and suggest solutions either by standardizing of existing behaviors or introducing new APIs. The goal is to facilitate the creation of fully-featured editing systems as well as small editors using JavaScript. + +The Task Force (TF) is part of the [W3C WebApps Working Group](https://w3c.github.io/webappswg/). The TF works primarily within its editing community on [Github](https://github.com/w3c/editing) and will report the results of its activities back to [W3C WebApps Working Group](https://www.w3.org/2019/webapps/). + +TF is leveraging the existing editing [GitHub](https://github.com/w3c/editing) repo with well-known locations and history of discussions on a variety of editing-related topics in order to “incubate” new editing-specific standards. + +This charter is intended to reflect on the current direction of the TF group, so that there is common agreement. It may be altered at any point in order to reflect new priorities or work items.  + +### 1. Scope + +The scope of Editing TF covers multiple aspects of editing, which may  include: + +- Textual input and text manipulation +- Text editing related events +- Selection +- Clipboard +- Spellcheck and grammar checking +- Reusing or discarding parts of or entire pre-existing editing APIs to serve as primitives of editing systems +- Standardization of under-specified existing editing related features +- Highlighting parts of text ranges without inducing DOM mutations. + +Experts who are contributing members of the task force will contribute to documents produced by the group, as described in the section on deliverables below.  + +### 2. Deliverables + +This Task Force will: + +- ensure that browsers are developing APIs that meet the expectations of editing framework authors of varying skill and team sizes.   +- allow a network of experts to share information about gaps and requirements for building editing frameworks on the web.  + +The specifications the Editing Taskforce is producing may be driven to the spec level directly by its members within the Web Applications Working Group, or be transferred to another, more appropriate working group after initial collection of requirements. Furthermore, the group defines its success as when it at the very least, produces a recommendation with well defined requirements that result in enhancing existing text editing related specification drafts or helps design new ones. + +The TF is expected to work on the following efforts until the end of the charter but it is not meant to be an exhaustive list: + +- [Async Clipboard API](https://bugs.chromium.org/p/chromium/issues/detail?id=931839) +- [ContentEditableDisabled](http://w3c.github.io/editing/contentEditableDisabled.html) - ability to disable system UI +- [EditContext API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/EditContext/explainer.md) +- [Highlight API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/explainer.md) +- Native Selection and Caret behaviors +- [SpellChecker API](https://github.com/w3c/editing/issues/166) +- [SIP Policy](https://github.com/whatwg/html/issues/4876) +- [Input Events](https://www.w3.org/TR/input-events-1/) +- [ContentEditable](https://w3c.github.io/contentEditable/) + +Deliverables are expected to eventually be shipped as Recommendations by the Web Applications Working Group, CSS Working Group or any other group where a draft specification may fall into. + +### 3. Participation + +This task force is designed to make participation relatively easy for people not currently involved in the standards process (typically, developers of editing tool libraries) who may not be amenable to signing up to a large in scope discussions that can be found in, for instance, the main Web Applications Working Group. + +**As per W3C IPR requirements, if a participant plans on making more than light editorial changes or propose new approaches and APIs, TF chairs will need to be notified and nominate you to become an [Invited Expert](https://www.w3.org/participate/invited-experts/).** + +The group encourages questions, comments and all technical discussions on its public [mailing list](https://lists.w3.org/Archives/Public/public-editing-tf/) and [document repositories](https://github.com/w3c/editing). + +Participants are reminded of the  [W3C's Code of Ethical Conduct](https://www.w3.org/Consortium/cepc/). + +### 4. Decision Policy + +The Editing Task force operates under the WebApps Working Group's [decision policy](https://www.w3.org/2019/05/webapps-charter.html#decisions) and adheres to the WebApps WG [working mode](https://www.w3.org/2019/05/webapps-charter.html#working-mode). diff --git a/README.md b/README.md index 901a0fb..602f32c 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,17 @@ -editing +Editing Task Force ================= -These are specifications and explainers developed by the Editing Task Force. For details, see [index.html](http://w3c.github.io/editing/). +These are specifications and explainers developed by the Editing Task Force. + +**Actively developed specs:** + +* See the [Editing Taskforce Charter](CHARTER.md) + + +**These specs are incomplete and it is not expected that they will advance beyond draft status:** + +* [Content Editable True](http://w3c.github.io/editing/contentEditableTrue.html) + +* [execCommand](http://w3c.github.io/editing/execCommand.html) + + diff --git a/index.html b/index.html deleted file mode 100644 index 0d73364..0000000 --- a/index.html +++ /dev/null @@ -1,199 +0,0 @@ - - - - - The Editing taskforce - - - - -
-

The Editing taskforce

- -

The Editing Task Force can be followed on our mailing list. We track issues in GitHub Issues as well.

- -

See the Task Force's charter for more information about the group.

- -
-
-

Specifications

- -

Actively developed specs:

- - -

Other specs also maintained:

- - -

Other editing related specs that are not maintained by the editing taskforce:

- -
- -
-

Introduction

-

- contenteditable - is used extensively on the web to enable users to directly edit HTML content. - However, it is very complex and its behavior is often largely overwritten - by sites or javascript frameworks. Completely overwriting it is very difficult - because it requires overwriting all keyboard shortcuts that perform commands - like bold and undo, as well as the context menu. Further, this must be done - in all supported languages. - A post on Medium tells one perspective of why it should be changed. -

- To further simplify the work of sites and frameworks, new types of contentEditable - simplifies default behavior to text input only, while providing local-specific - information on what a user intends such as to create newlines, delete content, - or format it. This allows sites to easily provide their own behaviors without - needing to handle complex text input like - IMEs. -

-
-
-

Framing the Problem

- -
-
-

Use Cases

- -
-
-

Goals

- -
-
-

Specs maintained

-

- It is a pattern in web editors that are built on top of contenteditable to disable some commanding functionality. - The reason for this is that consistency for Rich Text Editors is very hard, and requirements vary greatly from one app to the next. - Disabling all functionality is very difficult, however. -

-

In order to make it easier to disable specific capabilities of contenteditable, we are creating - different types of contenteditable with different features disabled by default in the - contentEditable spec.

-

Because it is widely used, contentEditable="true" will continue to be developed - in the contentEditable=True spec. Similarly, - the execCommand spec aims to spec the behavior of the execCommand command.

-
-
-

Acknowledgements

-

Thanks to: - Michael Aufreiter, - Adrian Bateman, - Oliver Buchtala, - Robin Berjon, - Enrica Casucci, - Olivier Forget, - Aryeh Gregor, - Marijn Haverbeke, - Yoshifumi Inoue, - Koji Ishii, - Gary Kacmarcik, - Frederico Caldeira Knabben, - Takayoshi Kochi, - Piotrek Koszuliński, - Travis Leithead, - Grisha Lyukshin, - Chaals McCathie Nevile, - Masayuki Nakano, - Ryosuke Niwa, - Julie Parent, - Ben Peters, - Florian Rivoal, - Morgan Smith, - Hallvord R. M. Steen, - Johan Sörlin, - Cristian Talau, - Dave Tapuska, - Ojan Vafai, - Léonie Watson, - Xiaoqian Wu, - Chong Zhang, - Joanmarie, - and everyone in the Editing Taskforce for their input and feedback. -

-
- - - diff --git a/tf-charter.html b/tf-charter.html deleted file mode 100644 index ae05b6a..0000000 --- a/tf-charter.html +++ /dev/null @@ -1,93 +0,0 @@ - - - - - HTML Editing Task Force Charter - - - - - -
-

- Editing on the Web, currently done through hacks sitting on top of contentEditable, - is generally acknowledged by all practitioners as a nightmare. -

-

- The goal of this task force is: -

To spec and standardize the behavior of contenteditable=true and existing editing APIs. -

-

To create a simpler alternative to contentEditable=true, which - creates primitives to allow for the creation of full-featured editing systems using JavaScript. -

-
-
-

Objectives

-

- The endgame for this group is to produce specifications that enable the creation of useful editing - systems on the Web, without requiring the many ugly hacks that are in common use today. -

-

- This covers multiple aspects, which include most notably: -

- -

- Deliverables are expected to be shipped as joint publications by both groups. -

-
-
-

Participation

-

- This task force is designed to - make participation relatively easy for people not currently involved in the standards process - (typically, developers of editing tool libraries) who may not be amenable to signing up to - the sort of "firehose" discussion that can be found in, for instance, the main Web Platform - list. -

-

- The decision and consensus policy - is the same as that which applies in the entire Web Platform group. -

-

- The group will use the Consortium's public-editing-tf - mail list for techical discussions. -

-
- -