diff --git a/CHARTER.md b/CHARTER.md
index efa7866b..e59ce268 100644
--- a/CHARTER.md
+++ b/CHARTER.md
@@ -44,7 +44,7 @@ The specifications the Editing Taskforce is producing may be driven to the spec
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/docs/contentEditableDisabled.html) - ability to disable system UI
+- [ContentEditableDisabled](http://w3c.github.io/editing/docs/contentEditableDisabled/) - 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
diff --git a/README.md b/README.md
index 2653c694..e042f6af 100644
--- a/README.md
+++ b/README.md
@@ -9,7 +9,7 @@ Details can be found in the [Editing Task Force Charter](https://github.com/w3c/
## Actively developed ideas/specs
-* [Content Editable Disabled](https://w3c.github.io/editing/docs/contentEditableDisabled.html)
+* [Content Editable Disabled](https://w3c.github.io/editing/docs/contentEditableDisabled/)
* [Virtual Keyboard Policy](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardPolicy/explainer.md)
* [EditContextAPI](docs/EditContext/explainer.md)
@@ -24,9 +24,9 @@ Details can be found in the [Editing Task Force Charter](https://github.com/w3c/
## Archive [3](#archivedFootnote)
-* [Content Editable True](http://w3c.github.io/editing/docs/inactive/contentEditableTrue.html)
+* [Content Editable True](http://w3c.github.io/editing/docs/contentEditableTrue/)
-* [execCommand](http://w3c.github.io/editing/docs/inactive/execCommand.html)
+* [execCommand](http://w3c.github.io/editing/docs/execCommand/)
## Process
diff --git a/TPAC/2019/Agenda.md b/TPAC/2019/Agenda.md
index ee789a75..b09102a3 100644
--- a/TPAC/2019/Agenda.md
+++ b/TPAC/2019/Agenda.md
@@ -3,7 +3,7 @@
Date: September 20th, 2019
Timing:
-- 8:30 - 9:15 EditContext
+- 8:30 - 9:15 EditContext
- 9:15 - 09:20 Break (5 mins)
- 9:20 - 10:05 EditContext
- 10:05 -10:20 Break (15 mins)
@@ -15,7 +15,7 @@ Timing:
- 13:45 - 13:50 Break (5 mins)
- 13:50 - 14:35 HighlightAPI
- 14:35 - 14:50 Break (15 mins)
-- 14:50 - 15:50 Undo Manager/Spellcheck API
+- 14:50 - 15:50 Undo Manager/Spellcheck API
- 15:50 - 16:35 Clipboard
- 16:25 - 16:40 Break (15 mins)
- 16:40 - 17:25 Clipboard
@@ -24,11 +24,11 @@ Timing:
## Topics:
- [EditContext API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/EditContext/explainer.md) (2 hours)
-
+
Objectives:
- [Highlight API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/explainer.md) (2 hours)
-
+
Objectives:
1. todo: provide links to the issues.
1. Static Ranges [applicability](https://github.com/whatwg/dom/issues/590)
@@ -36,9 +36,9 @@ Timing:
1. Range events
1. Is the proposal in a good enough shape to be moved into a spec draft phase? If so, is CSSWG a good place for it to live in?
-- [Remaining gaps in async clipboard API](https://bugs.chromium.org/p/chromium/issues/detail?id=931839) (2 hours)
-
- Objectives:
+- [Remaining gaps in async clipboard API](https://bugs.chromium.org/p/chromium/issues/detail?id=931839) (2 hours)
+
+ Objectives:
We are thinking of picking up the work where Chrome's team left of. Specifically, building support for html mime type and implementing clipboardChange event.
@@ -46,8 +46,8 @@ Timing:
Objectives:
-- [contenteditable-disabled](http://w3c.github.io/editing/contentEditableDisabled.html) (1 hour)
-
+- [contenteditable-disabled](http://w3c.github.io/editing/docs/contentEditableDisabled/) (1 hour)
+
Objectives:
- Spellcheck APIs (30minutes)- inspired by https://github.com/w3c/editing/issues/166.
@@ -57,12 +57,11 @@ Timing:
wanted to walk though use cases and hopefully, agree on the shape of the API if time allows.
- [SIP policy](https://github.com/whatwg/html/issues/4876) (30 mins)- we've received a request from Excel online and Google Docs asking for a way to control SIP. Excel's use case is to prevent SIP from showing up when editable element is focused. Google Docs has mentioned to have an explicit API for the virtual keyboard on touchscreen devices, particularly for showing/hiding the keyboard and querying its current state.. This is needed in cases where users would want to maintain editability of an element without invoking the SIP. We wanted to gauge interest in the community for this API
-
+
Objectives:
-
+
- [Undo Manager](https://whsieh.github.io/UndoManager/) (30 mins)- Give JavaScript a way to manipulate the browser's undo stack.
-
+
Objectives:
-
- [Spec Draft](https://rniwa.github.io/undo-api/)
+ [Spec Draft](https://rniwa.github.io/undo-api/)
diff --git a/contentEditableDisabled.html b/contentEditableDisabled.html
new file mode 100644
index 00000000..d840d001
--- /dev/null
+++ b/contentEditableDisabled.html
@@ -0,0 +1,10 @@
+
+
+Moved…
+
+Moved to
+https://w3c.github.io/editing/docs/contentEditableDisabled/
diff --git a/contentEditableEvents.html b/contentEditableEvents.html
new file mode 100644
index 00000000..84ff339d
--- /dev/null
+++ b/contentEditableEvents.html
@@ -0,0 +1,10 @@
+
+
+
Moved…
+
+Moved to
+https://w3c.github.io/contentEditable/
diff --git a/contentEditableTrue.html b/contentEditableTrue.html
new file mode 100644
index 00000000..6a8bef45
--- /dev/null
+++ b/contentEditableTrue.html
@@ -0,0 +1,10 @@
+
+
+
Moved…
+
+Moved to
+https://w3c.github.io/editing/docs/contentEditableTrue/
diff --git a/contentEditableTyping.html b/contentEditableTyping.html
new file mode 100644
index 00000000..84ff339d
--- /dev/null
+++ b/contentEditableTyping.html
@@ -0,0 +1,10 @@
+
+
+
Moved…
+
+Moved to
+https://w3c.github.io/contentEditable/
diff --git a/docs/graduated/contentEditable.html b/docs/contentEditable/index.html
similarity index 100%
rename from docs/graduated/contentEditable.html
rename to docs/contentEditable/index.html
diff --git a/docs/contentEditableDisabled.html b/docs/contentEditableDisabled/index.html
similarity index 99%
rename from docs/contentEditableDisabled.html
rename to docs/contentEditableDisabled/index.html
index ff67fa8c..62b204d3 100644
--- a/docs/contentEditableDisabled.html
+++ b/docs/contentEditableDisabled/index.html
@@ -12,7 +12,7 @@
mailto: "johannes@fiduswriter.org",
company: "Invited Expert"
}, ],
- github: "https://github.com/w3c/editing/docs/contentEditableDisabled.html",
+ github: "https://github.com/w3c/editing/docs/contentEditableDisabled/",
shortName: "contenteditable-interface",
wg: "Web Applications Working Group",
wgURI: "https://www.w3.org/2019/webapps/",
diff --git a/docs/inactive/contentEditableTrue.html b/docs/contentEditableTrue/index.html
similarity index 91%
rename from docs/inactive/contentEditableTrue.html
rename to docs/contentEditableTrue/index.html
index d58d3fec..8250cf64 100644
--- a/docs/inactive/contentEditableTrue.html
+++ b/docs/contentEditableTrue/index.html
@@ -32,7 +32,7 @@
, wg: "Web Applications Working Group"
, wgURI: "https://www.w3.org/2019/webapps/"
, wgPatentURI: "https://www.w3.org/2004/01/pp-impl/114929/status"
- , edDraftURI: "http://w3c.github.io/editing/docs/inactive/contentEditableTrue.html"
+ , edDraftURI: "http://w3c.github.io/editing/docs/contentEditableTrue/"
};
@@ -54,9 +54,9 @@
We need to figure out whether we want to continue working
on this document or not. If we keep the current division between execCommand
and contentEditable=True, we should likely move those things that are
- only contentEditable related from the execCommand
+ only contentEditable related from the execCommand
spec to this document. For example, some of the text concerning
- deletion of content may
+ deletion of content may
be more related to contentEditable = True.
@@ -78,7 +78,7 @@ Problem and Use Cases
contenteditable="true"
This section is not normative.
ContentEditable elements provide a caret that can be moved with the caret, and allow for the direction insertion of text at the position of the caret via the keyboard.
- ContentEditable elements can function as editing hosts for commands executed with execCommand.
+
ContentEditable elements can function as editing hosts for commands executed with execCommand.
Acknowledgements
diff --git a/docs/inactive/execCommand.html b/docs/execCommand/index.html
similarity index 99%
rename from docs/inactive/execCommand.html
rename to docs/execCommand/index.html
index 80aa88e7..2b6a057d 100644
--- a/docs/inactive/execCommand.html
+++ b/docs/execCommand/index.html
@@ -27,7 +27,7 @@
wgURI: "https://www.w3.org/2019/webapps/",
wgPublicList: "public-editing-tf",
wgPatentURI: "https://www.w3.org/2004/01/pp-impl/114929/status",
- edDraftURI: "https://w3c.github.io/editing/docs/inactive/execCommand.html",
+ edDraftURI: "https://w3c.github.io/editing/docs/execCommand/",
license: "cc0",
additionalCopyrightHolders:
"Copyright © 2015 This specification may be used under the terms of the CC0 1.0 Universal License and the W3C Community Contributor License Agreement (CLA). Thus anyone may reuse, modify, and redistribute them without restriction. W3C Editing APIs Community Group & W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply.",
diff --git a/docs/graduated/input-events.html b/docs/inputEvents/index.html
similarity index 100%
rename from docs/graduated/input-events.html
rename to docs/inputEvents/index.html
diff --git a/execCommand.html b/execCommand.html
new file mode 100644
index 00000000..19e50052
--- /dev/null
+++ b/execCommand.html
@@ -0,0 +1,10 @@
+
+
+Moved…
+
+Moved to
+https://w3c.github.io/editing/docs/execCommand/
diff --git a/input-events.html b/input-events.html
new file mode 100644
index 00000000..d96d2b64
--- /dev/null
+++ b/input-events.html
@@ -0,0 +1,10 @@
+
+
+
Moved…
+
+Moved to
+https://w3c.github.io/input-events/