From e2a1007e83a048619f97808380ab059bcd30e7dc Mon Sep 17 00:00:00 2001
From: Sanket Joshi <sajos@microsoft.com>
Date: Fri, 22 Dec 2023 15:41:18 -0800
Subject: [PATCH 1/2] [WritingSuggestions] Update explainer to propose new
 attribute instead of extending autocomplete.

---
 AutocompleteContentEditable/explainer.md      | 101 ------------------
 .../contact-details-suggestions-example.png   | Bin
 WritingSuggestions/explainer.md               |  56 ++++++++++
 .../facebook-post.png                         | Bin
 .../medium-draft.png                          | Bin
 .../youtube-video-comment.png                 | Bin
 6 files changed, 56 insertions(+), 101 deletions(-)
 delete mode 100644 AutocompleteContentEditable/explainer.md
 rename AutocompleteContentEditable/contact-details-autocomplete-example.png => WritingSuggestions/contact-details-suggestions-example.png (100%)
 create mode 100644 WritingSuggestions/explainer.md
 rename {AutocompleteContentEditable => WritingSuggestions}/facebook-post.png (100%)
 rename {AutocompleteContentEditable => WritingSuggestions}/medium-draft.png (100%)
 rename {AutocompleteContentEditable => WritingSuggestions}/youtube-video-comment.png (100%)

diff --git a/AutocompleteContentEditable/explainer.md b/AutocompleteContentEditable/explainer.md
deleted file mode 100644
index 00c207d47..000000000
--- a/AutocompleteContentEditable/explainer.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# Extending the Autocomplete Attribute to Editing Host Elements
-
-Consider all sections required unless otherwise noted.
-
-Authors: [Ben Mathwig](https://github.com/bmathwig), [Sanket Joshi](https://github.com/sanketj)
-
-## Status of this Document
-
-This document is a starting point for engaging the community and standards bodies in developing collaborative solutions fit for standardization. As the solutions to problems described in this document progress along the standards-track, we will retain this document as an archive and use this section to keep the community up-to-date with the most current standards venue and content location of future work and discussions.
-
-* This document status: **Active**
-* Expected venue: [WHATWG](https://whatwg.org/)
-* Current version: [Link](#)
-
-## Introduction
-The current specification for `autocomplete` allows for the attribute to exist on elements of type `<input>`, `<textarea>`, and `<select>`. With the popularity of text controls using an [editing host](https://html.spec.whatwg.org/multipage/interaction.html#editing-host), we should consider allowing [editing host](https://html.spec.whatwg.org/multipage/interaction.html#editing-host) elements to also utilize the `autocomplete` attribute. While not a common scenario within the scope of form fields, there are applications for text prediction and autofill within [editing host](https://html.spec.whatwg.org/multipage/interaction.html#editing-host) elements.
-
-## Goals
-Expand the definition of the `autocomplete` attribute to include [editing host](https://html.spec.whatwg.org/multipage/interaction.html#editing-host) elements as autocompletion targets. [4.10.18.7.1 Autofill](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute)
-
-## Use Case
-A developer may use the `autocomplete` attribute to take advantage of browser-provided writing assistance features like text prediction on `contenteditable` elements.
-
-### Facebook.com: Writing a post
-![Writing a post on facebook.com](facebook-post.png)
-
-### Medium.com: Drafting an article
-![Drafting an article on medium.com](medium-draft.png)
-
-### Youtube.com: Commenting on a video
-![Commenting on a video on youtube.com](youtube-video-comment.png)
-
-
-The `autocomplete` attribute could also be used to enable additional browser-provided autocompletion features in the future. See a hypothetical example below.
-
-![Contact details autocomplete example](contact-details-autocomplete-example.png)
-
-A developer may also turn off `autocomplete` for an [editing host](https://html.spec.whatwg.org/multipage/interaction.html#editing-host). For example, the site may provide their own custom writing assistance tools. The developer would be able to achieve this by setting `autocomplete=off`.
-
-## Out of Scope
-1. Defining expected user agent behavior or user interface design.
-2. Adding additional field names to the table for autofill values.
-
-## Proposed Solution
-We propose updating the group definitions in [4.10.18.7.1 Autofill](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute) to include [editing host](https://html.spec.whatwg.org/multipage/interaction.html#editing-host) elements in the *Text* and *Multiline* sections.
-
-**Before**
-```
-Text
-    input elements with a type attribute in the Hidden state
-    input elements with a type attribute in the Text state
-    input elements with a type attribute in the Search state
-    textarea elements
-    select elements
-Multiline
-    input elements with a type attribute in the Hidden state
-    textarea elements
-    select elements
-```
-
-**After**
-```
-Text
-    input elements with a type attribute in the Hidden state
-    input elements with a type attribute in the Text state
-    input elements with a type attribute in the Search state
-    textarea elements
-    select elements
-    editing host elements
-Multiline
-    input elements with a type attribute in the Hidden state
-    textarea elements
-    select elements
-    editing host elements
-```
-
-The text in [4.10.18.7.1 Autofill](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute) will also need to be updated to reflect that the `autocomplete` attribute can be used for editing scenarios and not just for form autofill.
-
-## Privacy and Security Considerations
-### Privacy
-The following section enumerates the potential security and privacy concerns identified during the development of this proposal and summarizes proposed solutions for each.
-
-| Concern | Description | Proposed Solution |
-| :- | :- | :- |
-| Autofill Data Storage Leak | Increasing the scope of applicable elements for autofill will increase the risk that autofill populates [editing host](https://html.spec.whatwg.org/multipage/interaction.html#editing-host) elements with sensitive information without user consent. | Form field elements like `<input>` already have autofill mechanisms in user agents where sensitive information such as address or phone number. We don't believe there are additional actions to take here and the existing mitigations for other elements still apply. |
-
-## Potential Extensions
-One potential extension is to add new field name values to the table to allow for more dynamic autofill population of content.
-
-## Alternative Solutions
-### Spellcheck Attribute
-The `spellcheck` attribute is specifically designed to control the browser's spellcheck and grammar check capabilities, therefore it is not semantically appropriate for control autocompletion.
-
-### Text Prediction Attribute
-A `textprediction` attribute could be introduced that takes `on/off` values, allowing developers to control whether the browser's text prediction is available on a text control. Such an attribute would be specific to text prediction and would not be future proof against additional types of autocompletion that browsers may introduce in the future.
-
-## Open Questions
-### Should the `autocomplete` attribute be supported on [EditContext editable hosts](https://w3c.github.io/edit-context/#dfn-editcontext-editing-host)?
-The [`EditContext` API](https://w3c.github.io/edit-context/) introduces a specialized editing host that enables editing applications to integrate with [text input services](https://w3c.github.io/edit-context/#dfn-text-input-service) without the [pitfalls of the browser's in-built text controls](https://w3c.github.io/edit-context/#background). Many sophisticated editors that could benefit from the `EditContext` API also integrate their own writing assistance features and thus may opt out of browser-powered autocompletion (ex. Google Docs, Word Online). Therefore, it is unclear whether supporting the `autocomplete` attribute on [EditContext editable hosts](https://w3c.github.io/edit-context/#dfn-editcontext-editing-host) will be useful.
-
-Implementation wise, when an `EditContext` is being edited, the UA does not directly update the DOM. Instead, content changes are communicated to the author via [events](https://w3c.github.io/edit-context/#editcontext-events) and the author is expected to commit those changes to the DOM in their custom way. To support browser-powered autocompletion in [EditContext editable hosts](https://w3c.github.io/edit-context/#dfn-editcontext-editing-host), a new type of event may need to be introduced to indicate to authors how/where to place the autocompletion suggestions.
\ No newline at end of file
diff --git a/AutocompleteContentEditable/contact-details-autocomplete-example.png b/WritingSuggestions/contact-details-suggestions-example.png
similarity index 100%
rename from AutocompleteContentEditable/contact-details-autocomplete-example.png
rename to WritingSuggestions/contact-details-suggestions-example.png
diff --git a/WritingSuggestions/explainer.md b/WritingSuggestions/explainer.md
new file mode 100644
index 000000000..69d1cf530
--- /dev/null
+++ b/WritingSuggestions/explainer.md
@@ -0,0 +1,56 @@
+# Writingsuggestions attribute to control UA-provided writing assistance
+
+Consider all sections required unless otherwise noted.
+
+Authors: [Sanket Joshi](https://github.com/sanketj)
+Previous authors: [Ben Mathwig](https://github.com/bmathwig)
+
+## Status of this Document
+
+This document is a starting point for engaging the community and standards bodies in developing collaborative solutions fit for standardization. As the solutions to problems described in this document progress along the standards-track, we will retain this document as an archive and use this section to keep the community up-to-date with the most current standards venue and content location of future work and discussions.
+
+* This document status: **Active**
+* Expected venue: [WHATWG](https://whatwg.org/)
+* Current version: [Link](#)
+
+## Introduction
+UAs are starting to provide writing suggestions to users as they type on various editable fields across the web (see the [use case](#use-case) section below). While this is
+generally useful for users, there are cases when developers may want to turn off UA-provided writing assistance, such as extensions or sites that wish to provide similar functionality on their own. To that end, this explainer proposes a solution that would allow developers to turn on/off UA-provided writing assistance.
+
+## Use Case
+A developer may use this control to take advantage of browser-provided writing assistance features like text prediction on `contenteditable` elements.
+
+### Facebook.com: Writing a post
+![Writing a post on facebook.com](facebook-post.png)
+
+### Medium.com: Drafting an article
+![Drafting an article on medium.com](medium-draft.png)
+
+### Youtube.com: Commenting on a video
+![Commenting on a video on youtube.com](youtube-video-comment.png)
+
+This control could also be used to enable additional browser-provided writing suggestions in the future. See a hypothetical example below.
+
+![Contact details suggestions example](contact-details-suggestions-example.png)
+
+A developer may also use this control to turn off browser-provided writing suggestions if they want to provide their own writing assistance tools.
+
+## Out of Scope
+1. Defining expected user agent behavior or user interface design.
+2. Styling of UA-provided writing suggestions.
+
+## Proposed Solution
+We propose the addition of a new attribute called `writingsuggestions` with values `on`/`off` that would allow developers to turn on/off browser-provided writing suggestions. This attribute will have a default state per element, as established by the UA. The attribute's state for an element can also be inherited from ancestor elements, thereby allowing developers to control this functionality at a per-element or per-document/sub-document scale.
+
+## Privacy and Security Considerations
+UAs may choose to provide users with personal settings to turn on/off writing assitance, similar to settings that are available for spellchecking. Similar to the `spellcheck` attribute, UAs must keep the values of the `writingsuggestions` attribute independent of the user's settings. Letting the user's setting influence the value of the attribute may introduce a new fingerprinting surface.
+
+## Alternative Solutions
+### Extending the `autocomplete` attribute to [editing hosts](https://html.spec.whatwg.org/multipage/interaction.html#editing-host)
+The `autocomplete` attribute is primarily designed for form fill scenarios and supports a [large number of values](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute), many of which are not applicable to writing scenarios. Reasoning about how each of these values should behave on editing hosts would be complex for browser and web developers alike.
+
+### Spellcheck Attribute
+The `spellcheck` attribute is specifically designed to control the browser's spellcheck and grammar check capabilities, therefore it is not semantically appropriate for controling writing suggestions.
+
+### Text Prediction Attribute
+A `textprediction` attribute could be introduced that takes `on/off` values, allowing developers to control whether the browser's text prediction is available on a text control. Such an attribute would be specific to text prediction and would not be future proof against additional types of writing suggestions that browsers may introduce in the future.
\ No newline at end of file
diff --git a/AutocompleteContentEditable/facebook-post.png b/WritingSuggestions/facebook-post.png
similarity index 100%
rename from AutocompleteContentEditable/facebook-post.png
rename to WritingSuggestions/facebook-post.png
diff --git a/AutocompleteContentEditable/medium-draft.png b/WritingSuggestions/medium-draft.png
similarity index 100%
rename from AutocompleteContentEditable/medium-draft.png
rename to WritingSuggestions/medium-draft.png
diff --git a/AutocompleteContentEditable/youtube-video-comment.png b/WritingSuggestions/youtube-video-comment.png
similarity index 100%
rename from AutocompleteContentEditable/youtube-video-comment.png
rename to WritingSuggestions/youtube-video-comment.png

From f80a484b73f539ff8a1af7589aab325cea9983e4 Mon Sep 17 00:00:00 2001
From: Sanket Joshi <sajos@microsoft.com>
Date: Fri, 22 Dec 2023 16:04:32 -0800
Subject: [PATCH 2/2] Update README to reflect name change.

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c54fb18aa..2ec0151cd 100644
--- a/README.md
+++ b/README.md
@@ -60,7 +60,7 @@ we move them into the [Alumni section](#alumni-) below.
 | [Pen Events](PenEvents/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/Pen%20Events"> ![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/Pen%20Events?label=issues)</a> | [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=BoCupp-Microsoft%2C+gked&labels=Pen+Events&template=pen-events.md&title=%5BPenEvents%5D+%3CTITLE+HERE%3E) | Editing |
 | [Pen Action](PenAction/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/Pen%20Action"> ![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/Pen%20Action?label=issues)</a> | [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=BoCupp-Microsoft%2C+gked&labels=Pen+Action&template=pen-action.md&title=%5Bpen-action%5D+%3CTITLE+HERE%3E) | Editing |
 | [Delayed Clipboard Rendering](DelayedClipboard/DelayedClipboardRenderingExplainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/Delayed%20Clipboard%20Rendering"> ![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/Delayed%20Clipboard%20Rendering?label=issues)</a> | [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=anaskim&labels=Delayed+Clipboard+Rendering&template=delayed-clipboard-rendering.md&title=%5BDelayed+Clipboard+Rendering%5D+%3CTITLE+HERE%3E) | Editing |
-| [Autocomplete Supports Edit Host Elements](AutocompleteContentEditable/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/AutocompleteEditHost">![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/AutocompleteEditHost?label=issues)</a> | [New Issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=bmathwig&labels=AutocompleteEditHost&template=autocomplete-edit-host.md&title=%5BAutocompleteEditHost%5D+Issue) | Editing |
+| [WritingSuggestions attribute](WritingSuggestions/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/WritingSuggestions">![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/WritingSuggestions?label=issues)</a> | [New Issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=sajos&labels=WritingSuggestions&template=WritingSuggestions-edit-host.md&title=%5BWritingSuggestions%5D+Issue) | HTML/Editing |
 | [Source Hashes in Stack Traces](DevTools/SourceHash/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/Source+hash"> ![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/Source+hash?label=issues)</a> | [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=robpaveza&labels=Source+hash&title=%5BSource+Hashes%5D+%3CTITLE+HERE%3E) | JavaScript |
 | [PerformanceNavigationTiming User Agent Launch](PerformanceNavigationTiming%20for%20User%20Agent%20Launch/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/Perf%20timing%20during%20browser%20start">![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/Perf%20timing%20during%20browser%20start?label=issues)</a> | [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=dylank%2C+hemingzh&labels=Perf+timing+during+browser+start&template=performance-timing-during-browser-start.md&title=%5BPerf+Timing+during+launch%5D+%3CTITLE+HERE%3E) | Performance |
 | [PerformanceNavigationTiming Protocol Launch](PerformanceNavigationTiming%20changes%20for%20protocol%20launch/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/PerformanceNavigationTiming%20for%20Protocol%20Launch">![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/PerformanceNavigationTiming%20for%20Protocol%20Launch?label=issues)</a> | [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=atulkatti&labels=PerformanceNavigationTiming+for+Protocol+Launch&template=performancenavigationtiming-protocol-launch-timing-information.md&title=) | Performance |