Skip to content

Latest commit

 

History

History
73 lines (43 loc) · 5.55 KB

CHARTER.md

File metadata and controls

73 lines (43 loc) · 5.55 KB
Raw

End Date: 31 May 2021 

Confidentiality: Proceedings are public 

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. The TF works primarily within its editing community on Github and will report the results of its activities back to  W3C WebApps Working Group.

TF is leveraging the existing editing GitHub 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:

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 and document repositories.

Participants are reminded of the  W3C's Code of Ethical Conduct.

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