From 01cb0bc9c0019b6a750a7bcced26b9d2c61f597e Mon Sep 17 00:00:00 2001 From: Johannes Wilm Date: Fri, 18 Oct 2019 19:47:42 +0200 Subject: [PATCH 01/14] update charter --- CHARTER.md | 91 +++++++++++++++++++++++++++++++++++++++++++++++ tf-charter.html | 93 ------------------------------------------------- 2 files changed, 91 insertions(+), 93 deletions(-) create mode 100644 CHARTER.md delete mode 100644 tf-charter.html diff --git a/CHARTER.md b/CHARTER.md new file mode 100644 index 0000000..3550376 --- /dev/null +++ b/CHARTER.md @@ -0,0 +1,91 @@ +**End Date:** 31 May 2021  + +**Confidentiality:** Proceedings are [public](https://www.w3.org/2005/10/Process-20051014/comm.html#confidentiality-levels)  + +**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 existing 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 full-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://w3c.github.io/webappswg/). + +  + +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 standards recommendation 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. + +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 + +Editing Task Force group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its chair(s) will put a question about the issue to the group and gather responses (including any formal objections to formally publishing a document into the appropriate WG); then, after due consideration of all the responses, the Chair(s) will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).  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. -

-
- - From 9c71ad1f684dfe4280786e5739125496dc4ba74f Mon Sep 17 00:00:00 2001 From: Johannes Wilm Date: Fri, 18 Oct 2019 20:14:59 +0200 Subject: [PATCH 02/14] delete extra lines --- CHARTER.md | 24 +----------------------- 1 file changed, 1 insertion(+), 23 deletions(-) diff --git a/CHARTER.md b/CHARTER.md index 3550376..fe4dc0b 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -8,29 +8,16 @@ ### 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 existing 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 full-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://w3c.github.io/webappswg/). -  - 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: @@ -44,19 +31,12 @@ The scope of Editing TF covers multiple aspects of editing, which may  include: - 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.  @@ -84,8 +64,6 @@ The group encourages questions, comments and all technical discussions on its pu Participants are reminded of the  [W3C's Code of Ethical Conduct](https://www.w3.org/Consortium/cepc/). - - ### 4. Decision Policy -Editing Task Force group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its chair(s) will put a question about the issue to the group and gather responses (including any formal objections to formally publishing a document into the appropriate WG); then, after due consideration of all the responses, the Chair(s) will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).  +Editing Task Force group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its chair(s) will put a question about the issue to the group and gather responses (including any formal objections to formally publishing a document into the appropriate WG); then, after due consideration of all the responses, the Chair(s) will record a group resolution (possibly after a formal vote and also along with responding to any formal objections). From 2615fbe1e8a128a8983b900de411b62fc31ad77b Mon Sep 17 00:00:00 2001 From: Johannes Wilm Date: Fri, 18 Oct 2019 20:28:45 +0200 Subject: [PATCH 03/14] move links index.html => README.md --- README.md | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) 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) + + From 8e7092b310ff9fca1372db66b17259edf5d45da1 Mon Sep 17 00:00:00 2001 From: Johannes Wilm Date: Fri, 18 Oct 2019 20:29:26 +0200 Subject: [PATCH 04/14] Delete index.html --- index.html | 199 ----------------------------------------------------- 1 file changed, 199 deletions(-) delete mode 100644 index.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

-
    -
  • ContentEditable is too complex and buggy to be usable as-is -
    While we could solve this by spec'ing contentEditable's behavior, the remaining issues here cause us to look in a new direction instead. -
  • ContentEditable does not easily enable the wide range of editing scenarios. - It is high-level and not supportive of the principles listed in the - Extensible Web Manifesto. -
    • -
-
-
-

Use Cases

-
  • Semantic HTML WYSIWYG editor for a blogging platform or email. (link to mail) -

    The editor needs to able to add both semantic and visual annotation to the document as it will be published as a blog. - Headings are to be marked up with h1. h2, etc... and each acronyms, abbreviations, and so forth are marked up with respective HTML elements. - However, the editor also supports visual annotations such as bolding, italicizing, and enlarging text, - each of which will be interpreted by the editor to respective underlying semantics in HTML. -

    More Info: In order to keep things consistent he may want to disallow certain types of styling. - A few years ago it was common to see people with Joomla sites who just pasted the text into the editor after copying it from a word processor. - Each blog post therefore ended up having very different styling. -

    More thoughts (From Microsoft): -
    In addition to the functionality mentioned above, the editor should support more advanced markup operations like handling bullets/indentation, - tables, and clear formatting (in heavily nested HTML) that are not consistent across browsers today. -
    Scenarios: -

    • Prevent style bleeding between the app and the body of the draft mail -
    • Remember cursor position (or selected range) when focus is out of editor - formatting bar buttons, or insert image cases -
    • Extensible and consistent paste mode across browsers - e.g. paste AS-IS HTML, paste clean HTML (aka merge formatting), and paste text only -
    • Extensibility for formatting commands - e.g. when browser handles the bullets it allows callback to javascript to define customized behavior; - on under a nested bullet structure, some browsers add a new bullet, others create a new line without bullet and delete the previous bullet; - Merge two lists using delete/backspace, instead of keeping two different list structures -

    -
  • Structured content editor with whitelisted DOM elements and/or classes. (link to mail) -
    Part of the point is to keep the structure of the document semantically defined. - Users can't change font sizes of individual words, etc. - This is because one of the main tasks of scientific journal editors who currently receive drafts in Word or Libreoffice - format have to undo all the manual styling the writers have added in order to get everything to look in a similar way. - We simply take those styling possibilities away so that we can define the entire design through one stylesheet as well as easily convert to other formats, - such as LaTex or an Epub, and be sure that we cover all formatting tags that were used. -
  • Editor that supports areas of non-editable content, nested editable content, etc (see what CKEditor are doing with widgets.) - (link to mail) -
    We also do that - for example in the case of formulas. - Generally the text is editable near-Wysiwyg style. - But when it comes to formulas, we let the user enter them in Latex format and display the result using mathjax. - Each formula object within the text is a noneditable island. If the user clicks on it with the mouse, he can change the formula. -
    Another example are figures: We want them to always be block elements and to have exactly one caption without styling. - They are therefore non-editable islands and if the user clicks on them he can change the figure's display and the caption text. -
  • Web-based code editor with syntax highlighting, etc. (link to mail) -
  • Browser based "word art" generator where end-user types some text and it renders in 3D along a curve and in rainbow colors on a <canvas>. - (link to mail) -
  • Track changes functionality within an editor (like https://github.com/NYTimes/ice ) -
    (really should be run MVC in order to keep the code somewhat readable. Currently ICE breaks whenever any of the browser makers decide to change anything about contenteditable.) -
  • Web-based DTP application (link to mail) -
    The app can creates a document that contains pagination, columns, and a complex illustrations. - It needs to let users edit any text that appears in the document. - Each editable text needs to be accessible, and styles applied to text need to be backed by the application's internal model of the document. -
  • Surface for plain text editing (From Microsoft) -
    Plain-text emails require a formatting surface that strips out any HTML tags, and prevents them from being entered (e.g. via copy paste) -
  • Style read-only text (From Microsoft) -
    The sample text is read only, but is possible to change the format of the text. This is used to select default compose font properties (text font, size, color, BIU). -
-
-
-

Goals

-
  • Empower authors with the right set of baseline behavior to enable creating complex editors -
  • Make it easy to implement custom behavior with appropriate APIs -
  • Allow overwrite of behavior for a user intention from all actions that indicate that intention -
  • Empower complex editors to be accessible by enabling users to understand available behaviors with little accessibility-specific work from the framework or site -
-
-
-

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. -

-
- - - From 49a5d8695817edd4dc6dc271454fcb4df5f1e083 Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Fri, 18 Oct 2019 15:43:11 -0700 Subject: [PATCH 05/14] Update CHARTER.md killing some extra lines and removing redundant word --- CHARTER.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/CHARTER.md b/CHARTER.md index fe4dc0b..708ab50 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -8,15 +8,18 @@ ### 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 existing 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 full-featured editing systems as well as small editors using JavaScript.  +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://w3c.github.io/webappswg/). 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 @@ -32,11 +35,11 @@ The scope of Editing TF covers multiple aspects of editing, which may  include: - 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.  @@ -64,6 +67,7 @@ The group encourages questions, comments and all technical discussions on its pu Participants are reminded of the  [W3C's Code of Ethical Conduct](https://www.w3.org/Consortium/cepc/). + ### 4. Decision Policy -Editing Task Force group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its chair(s) will put a question about the issue to the group and gather responses (including any formal objections to formally publishing a document into the appropriate WG); then, after due consideration of all the responses, the Chair(s) will record a group resolution (possibly after a formal vote and also along with responding to any formal objections). +Editing Task Force group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its chair(s) will put a question about the issue to the group and gather responses (including any formal objections to formally publishing a document into the appropriate WG); then, after due consideration of all the responses, the Chair(s) will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).  From d70ab511c2b18d15be04f31620d77b85155de92e Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Fri, 18 Oct 2019 15:44:20 -0700 Subject: [PATCH 06/14] Update CHARTER.md --- CHARTER.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/CHARTER.md b/CHARTER.md index 708ab50..6e8b19a 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -8,8 +8,6 @@ ### 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.  From 830b1107713b8b1381e5d858dd90b110cd65dff2 Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Mon, 4 Nov 2019 15:44:41 -0800 Subject: [PATCH 07/14] Update CHARTER.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Marcos Cáceres --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index 6e8b19a..cf3130c 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -12,7 +12,7 @@ Enabling rich editing experience on the web is currently a challenging task. Rea 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://w3c.github.io/webappswg/). +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. From f4cf96142d9b3effedbfb1c9f18d1beda18e0f8e Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Mon, 4 Nov 2019 15:45:17 -0800 Subject: [PATCH 08/14] Update CHARTER.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Marcos Cáceres --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index cf3130c..343aaed 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -55,7 +55,7 @@ The TF is expected to work on the following efforts until the end of the charter - [Input Events](https://www.w3.org/TR/input-events-1/) - [ContentEditable](https://w3c.github.io/contentEditable/) -Deliverables are expected to eventually be shipped as standards recommendation by the Web Applications Working Group, CSS Working Group or any other group where a draft specification may fall into. +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 From e743aa3dbfb0db18f4d91338dcd646fed8677063 Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Mon, 4 Nov 2019 15:53:02 -0800 Subject: [PATCH 09/14] Update CHARTER.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Marcos Cáceres --- CHARTER.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index 343aaed..ae02a9a 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -1,4 +1,3 @@ -**End Date:** 31 May 2021  **Confidentiality:** Proceedings are [public](https://www.w3.org/2005/10/Process-20051014/comm.html#confidentiality-levels)  From e773bcdbfc5ab7e8b51d2fad2eddcf2c2702b66f Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Wed, 6 Nov 2019 11:51:28 -0800 Subject: [PATCH 10/14] Update CHARTER.md --- CHARTER.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CHARTER.md b/CHARTER.md index ae02a9a..7bd80c3 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -60,6 +60,8 @@ Deliverables are expected to eventually be shipped as Recommendations by the Web 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. + 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/). From 4fdd6014c6f74ff35d4449acebf1d0f9d9c13a7d Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Fri, 8 Nov 2019 13:45:49 -0800 Subject: [PATCH 11/14] Update CHARTER.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Marcos Cáceres --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index 7bd80c3..a64258e 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -69,4 +69,4 @@ Participants are reminded of the  [W3C's Code of Ethical Conduct](https://www.w ### 4. Decision Policy -Editing Task Force group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its chair(s) will put a question about the issue to the group and gather responses (including any formal objections to formally publishing a document into the appropriate WG); then, after due consideration of all the responses, the Chair(s) will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).  +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). From 029edc101658ac4c5c69d30ec4c3318ac68feb63 Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Fri, 8 Nov 2019 13:48:41 -0800 Subject: [PATCH 12/14] Update CHARTER.md adding "acting as delegates from the WG chairs" to the chairs. --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index a64258e..d80f142 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -1,7 +1,7 @@ **Confidentiality:** Proceedings are [public](https://www.w3.org/2005/10/Process-20051014/comm.html#confidentiality-levels)  -**Chairs:** Johannes Wilm (Invited Expert), Grisha Lyukshin (Microsoft) +**Chairs(acting as delegates from the 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.  From 8dea85c6b29f905dfed3f5b8f5387a1fd57aca84 Mon Sep 17 00:00:00 2001 From: Grisha Lyukshin Date: Fri, 8 Nov 2019 13:57:22 -0800 Subject: [PATCH 13/14] Update CHARTER.md --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index d80f142..c2ff1f2 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -1,7 +1,7 @@ **Confidentiality:** Proceedings are [public](https://www.w3.org/2005/10/Process-20051014/comm.html#confidentiality-levels)  -**Chairs(acting as delegates from the WG chairs):** Johannes Wilm (Invited Expert), Grisha Lyukshin (Microsoft) +**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.  From e7b122a3560cc5602800e2742ffe4469cfcf7194 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20C=C3=A1ceres?= Date: Sat, 9 Nov 2019 14:43:45 +1100 Subject: [PATCH 14/14] Editorial, whitespace cleanup, link to IE page --- CHARTER.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/CHARTER.md b/CHARTER.md index c2ff1f2..48e3fe1 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -7,16 +7,15 @@ ### 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. +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.  +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/). +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 @@ -32,11 +31,11 @@ The scope of Editing TF covers multiple aspects of editing, which may  include: - 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 +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.  @@ -60,13 +59,12 @@ Deliverables are expected to eventually be shipped as Recommendations by the Web 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. +**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).