Web Editing Working Group - Activity in 2026
No matches.
TR publications
-
1 document published.
-
Input Events Level 2 published as a Working Draft. History of Input Events Level 2
-
Past meetings
-
1 meeting.
GitHub
w3c/selection-api
-
1 issue opened.
-
Feature: API to convert Selection into a URL w3c/selection-api#362, by @martinthomson.
-
-
1 issue received 1 new comment.
-
`anchorNode` & `focusNode` can never be in shadow tree? w3c/selection-api#361 (1 comment by @smaug----)
-
w3c/input-events
-
3 pull requests opened.
-
Add note on handling synthetic beforeinput events dispatched by extensions w3c/input-events#185, by @johanneswilm.
-
Import UI-Events input events w3c/input-events#184, by @johanneswilm.
-
specify that InputEvents can be initialized with target ranges from script w3c/input-events#183, by @johanneswilm.
-
-
2 pull requests merged.
-
specify that InputEvents can be initialized with target ranges from script w3c/input-events#183.
-
Add note on handling synthetic beforeinput events dispatched by extensions w3c/input-events#185.
-
-
3 pull requests received 6 new comments.
-
Add note on handling synthetic beforeinput events dispatched by extensions w3c/input-events#185 (4 comments by @GaurangTandon, @johanneswilm)
-
specify that InputEvents can be initialized with target ranges from script w3c/input-events#183 (1 comment by @johanneswilm)
-
w3c/edit-context
-
6 issues opened.
-
Allow lazy / pull-on-demand text and selection updates for EditContext w3c/edit-context#156, by @GaryKlassen.
-
Should more `insertFrom*` be EditContext-handled? w3c/edit-context#155, by @ltenmoz.
-
using contenteditable="false" to control caret movement w3c/edit-context#154, by @johanneswilm.
-
missing beforeinput w3c/edit-context#153, by @johanneswilm.
-
make EditContexts hosts discoverable from extensions w3c/edit-context#152, by @johanneswilm.
-
Could canvas-based EditContext be removed? w3c/edit-context#151, by @ltenmoz.
-
-
1 issue closed.
-
missing beforeinput w3c/edit-context#153.
-
-
5 issues received 24 new comments.
-
Should `beforeinput` be fired for composition? If so what should the target ranges be? w3c/edit-context#133 (13 comments by @johanneswilm, @ltenmoz, @masayuki-nakano)
-
make EditContexts hosts discoverable from extensions w3c/edit-context#152 (2 comments by @GaurangTandon, @ltenmoz)
-
w3c/editing
-
1 issue opened.
-
1 issue closed.
-
forming of community editing group w3c/editing#541.
-
-
3 issues received 18 new comments.
-
Universal interface to modify content in a JS editor from unrelated JS code. w3c/editing#551 (16 comments by @GaurangTandon, @johanneswilm)
-
w3c/editing#200 (1 comment by @GaurangTandon)
-
-
2 pull requests merged.
-
Actually return true from forwarddelete w3c/editing#544.
-
Actually return true from indent command w3c/editing#547.
-
-
2 pull requests received 4 new comments.
TR publications
-
2 documents published.
-
EditContext API published twice as a Working Draft. History of EditContext API
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Gaurang Tandon (W3C Invited Experts) joined.
-
-
2 participants left.
-
Samba Murthy Bandaru (Microsoft Corporation) left.
-
Ashish Kumar (Microsoft Corporation) left.
-
-
1 organization left.
-
Bocoup left.
-
GitHub
w3c/editing
-
5 issues received 7 new comments.
-
Add ability to control native undo/redo stack w3c/editing#509 (3 comments by @johanneswilm, @michael, @smaug----)
-
iOS Safari: URL bar invisible hitbox overlaps text selection grab circle w3c/editing#550 (1 comment by @michael)
-
iOS Safari: Support meta content="interactive-widget=resizes-content" w3c/editing#549 (1 comment by @michael)
-
Chrome: Selection barrier at details element when contenteditable=true w3c/editing#538 (1 comment by @ssddanbrown)
-
w3c/clipboard-apis
-
3 issues received 4 new comments.
-
Standardize Clipboard Source url, aka the URL from which the content has been copied from w3c/clipboard-apis#244 (2 comments by @ericlaw1979, @evilpie)
-
w3c/edit-context
-
1 issue closed.
-
Improve discussion of accessibility in explainer w3c/edit-context#136.
-
-
4 issues received 5 new comments.
-
2 pull requests merged.
-
Add "Accessibility" section to explainer and spec w3c/edit-context#146.
-
Specify what TextUpdateEvent updateRangeStart/End should be set to. w3c/edit-context#130.
-
-
4 pull requests received 6 new comments.
-
Add selection range checks to updateSelection, updateText and EditContext constructor. w3c/edit-context#144 (3 comments by @dandclark, @smaug----)
-
Specify what TextUpdateEvent updateRangeStart/End should be set to. w3c/edit-context#130 (1 comment by @dandclark)
-
w3c/selection-api
-
1 issue received 2 new comments.
-
`anchorNode` & `focusNode` can never be in shadow tree? w3c/selection-api#361 (2 comments by @annevk, @dandclark)
-
Past meetings
-
1 meeting.
GitHub
w3c/edit-context
-
2 issues opened.
-
Accessibility API mapping for EditContext editors w3c/edit-context#150, by @ltenmoz.
-
EditContext needs a way to inform IMEs of vertical writing modes w3c/edit-context#149, by @dandclark.
-
-
6 issues received 10 new comments.
-
Improve timing for Update the Text Edit Context w3c/edit-context#127 (3 comments by @johanneswilm, @ltenmoz, @smaug----)
-
EditContext needs a way to inform IMEs of vertical writing modes w3c/edit-context#149 (2 comments by @karintou8710, @tkent-google)
-
Should we add TextFormat.textColor back? w3c/edit-context#54 (2 comments by @johanneswilm, @smaug----)
-
Should `beforeinput` be fired for composition? If so what should the target ranges be? w3c/edit-context#133 (1 comment by @johanneswilm)
-
Should updateCharacterBounds() throw an error if the bounds are out of range of the text? w3c/edit-context#142 (1 comment by @dandclark)
-
-
3 pull requests opened.
-
Fix broken links to "layout viewport" w3c/edit-context#148, by @tidoust.
-
Dispatch textformatupdate with empty format list when deactivating EditContext w3c/edit-context#147, by @ltenmoz.
-
Add "Accessibility" section to explainer and spec w3c/edit-context#146, by @ltenmoz.
-
-
4 pull requests received 30 new comments.
-
Add "Accessibility" section to explainer and spec w3c/edit-context#146 (25 comments by @dandclark, @jcsteh, @ltenmoz, @smaug----)
-
Add selection range checks to updateSelection, updateText and EditContext constructor. w3c/edit-context#144 (3 comments by @dandclark, @ltenmoz, @smaug----)
-
w3c/selection-api
-
1 issue opened.
-
`anchorNode` & `focusNode` can never be in shadow tree? w3c/selection-api#361, by @yezhizhen.
-
w3c/editing
-
3 issues opened.
-
iOS Safari: URL bar invisible hitbox overlaps text selection grab circle w3c/editing#550, by @michael.
-
iOS Safari: Support meta content="interactive-widget=resizes-content" w3c/editing#549, by @michael.
-
Safari: incorrect keyboard state w3c/editing#548, by @johanneswilm.
-
-
4 issues received 5 new comments.
-
When should metadata-content elements like <style> be editable? w3c/editing#546 (1 comment by @masayuki-nakano)
-
Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization w3c/editing#542 (1 comment by @johanneswilm)
-
Chrome: Selection barrier at details element when contenteditable=true w3c/editing#538 (1 comment by @johanneswilm)
w3c/input-events
-
1 issue received 1 new comment.
Lifecycle
-
1 charter started.
-
Chartered until 22 July 2028.
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Joanne Pan (Apple Inc.) joined.
-
Cole Carley (Apple Inc.) joined.
-
GitHub
w3c/editing
-
4 issues opened.
-
When should metadata-content elements like <style> be editable? w3c/editing#546, by @dandclark.
-
Spec for InsertImage command is (no longer) 'correct'. w3c/editing#543, by @Psychpsyo.
-
-
4 issues received 5 new comments.
-
Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization w3c/editing#542 (2 comments by @michael)
-
Chrome: Selection barrier at details element when contenteditable=true w3c/editing#538 (1 comment by @michael)
-
-
2 pull requests opened.
-
Actually return true from indent command w3c/editing#547, by @Psychpsyo.
-
Actually return true from forwarddelete w3c/editing#544, by @Psychpsyo.
-
w3c/clipboard-apis
-
2 issues opened.
-
"allowed to show a popup" definition link goes nowhere w3c/clipboard-apis#250, by @AtkinsSJ.
-
2 issues closed.
-
Remove clipboardchange event (and replace it possibly with a promise returning method) w3c/clipboard-apis#228.
-
ClipboardChange even spec: Callout details for cross-origin iframes and fencedframes w3c/clipboard-apis#226.
-
-
3 issues received 3 new comments.
-
Remove clipboardchange event (and replace it possibly with a promise returning method) w3c/clipboard-apis#228 (1 comment by @dandclark)
-
ClipboardChange even spec: Callout details for cross-origin iframes and fencedframes w3c/clipboard-apis#226 (1 comment by @dandclark)
-
Option to specify ClipboardItem is sensitive in .write() and .writeText() w3c/clipboard-apis#154 (1 comment by @dillonstreator)
-
w3c/edit-context
-
3 issues opened.
-
Should updateCharacterBounds() throw an error if the bounds are out of range of the text? w3c/edit-context#142, by @ltenmoz.
-
Support Begin Batch Edit and End Batch Edit for Edit Context w3c/edit-context#141, by @hd-chuong.
-
How should canvas EditContext be made accessible? w3c/edit-context#139, by @ltenmoz.
-
-
4 issues received 14 new comments.
-
Should `beforeinput` be fired for composition? If so what should the target ranges be? w3c/edit-context#133 (9 comments by @hsinyi, @ltenmoz, @masayuki-nakano, @michael)
-
Support Begin Batch Edit and End Batch Edit for Edit Context w3c/edit-context#141 (3 comments by @hd-chuong, @ltenmoz)
-
-
4 pull requests opened.
-
Add getText() method for retrieving a substring of the text. w3c/edit-context#145, by @ltenmoz.
-
Add selection range checks to updateSelection, updateText and EditContext constructor. w3c/edit-context#144, by @ltenmoz.
-
Add range check to updateCharacterBounds(). w3c/edit-context#143, by @ltenmoz.
-
Add TextFormat.textColor and TextFormat.backgroundColor. w3c/edit-context#140, by @ltenmoz.
-
-
1 pull request merged.
-
Clean up deactivating EditContext w3c/edit-context#123.
-
-
1 pull request received 2 new comments.
-
Add selection range checks to updateSelection, updateText and EditContext constructor. w3c/edit-context#144 (2 comments by @ltenmoz)
-
w3c/input-events
-
2 issues opened.
-
Add borders to the cells of the tables to improve readability w3c/input-events#182, by @AndresMunozDeveloper.
-
non-cancelable deleteContentBackward in Chromium w3c/input-events#181, by @johanneswilm.
-
TR publications
-
6 documents published.
-
Clipboard API and events published as a Working Draft. History of Clipboard API and events
-
EditContext API published 3 times as a Working Draft. History of EditContext API
-
Selection API published twice as a Working Draft. History of Selection API
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Leo Tenenbaum (Mozilla Foundation) joined.
-
GitHub
w3c/edit-context
-
6 issues opened.
-
Should textformatupdate be fired with empty formats array when EditContext is deactivated? w3c/edit-context#138, by @ltenmoz.
-
[meta] Blockers for Gecko EditContext implementation w3c/edit-context#137, by @ltenmoz.
-
Improve discussion of accessibility in explainer w3c/edit-context#136, by @ltenmoz.
-
"double" underline style was removed, but it may be used by some IMEs w3c/edit-context#135, by @ltenmoz.
-
Should `beforeinput` be fired for composition? If so what should the target ranges be? w3c/edit-context#133, by @ltenmoz.
-
BiDi input handling is difficult with DOM-based EditContext w3c/edit-context#132, by @ltenmoz.
-
-
2 issues closed.
-
BiDi input handling is difficult with DOM-based EditContext w3c/edit-context#132.
-
-
1 issue reopened.
-
Should we add TextFormat.textColor back? w3c/edit-context#54, by @dandclark.
-
-
6 issues received 17 new comments.
-
Should we add TextFormat.textColor back? w3c/edit-context#54 (6 comments by @ltenmoz, @masayuki-nakano, @smaug----)
-
BiDi input handling is difficult with DOM-based EditContext w3c/edit-context#132 (6 comments by @jfkthame, @ltenmoz, @smaug----)
-
Improve timing for Update the Text Edit Context w3c/edit-context#127 (2 comments by @dandclark, @ltenmoz)
-
Should `beforeinput` be fired for composition? If so what should the target ranges be? w3c/edit-context#133 (1 comment by @ltenmoz)
-
-
1 pull request opened.
-
Remove beforeinput spec issue note w3c/edit-context#134, by @ashishkum-ms.
-
-
3 pull requests merged.
-
Remove beforeinput spec issue note w3c/edit-context#134.
-
Add default values to `*Init` dictionaries w3c/edit-context#125.
-
Remove `compositionStart`/`End` from TextUpdateEventInit. w3c/edit-context#122.
-
-
2 pull requests received 2 new comments.
-
Remove `compositionStart`/`End` from TextUpdateEventInit. w3c/edit-context#122 (1 comment by @dandclark)
w3c/editing
-
3 issues opened.
-
forming of community editing group w3c/editing#541, by @johanneswilm.
-
Participation at TPAC 2026? w3c/editing#540, by @johanneswilm.
-
Chrome: Selection barrier at details element when contenteditable=true w3c/editing#538, by @michael.
-
-
4 issues received 6 new comments.
-
Behavior of insert* commands for contenteditable=plaintext-only w3c/editing#419 (1 comment by @masayuki-nakano)
-
3 pull requests opened.
-
Repro for #538 w3c/editing#539, by @michael.
-
[execCommand] Add a GitHub link w3c/editing#537, by @zcorpan.
-
execCommand: use range's collapsed concept instead of public API w3c/editing#536, by @annevk.
-
-
3 pull requests merged.
-
[execCommand] Add a GitHub link w3c/editing#537.
-
Repro for #538 w3c/editing#539.
-
execCommand: use range's collapsed concept instead of public API w3c/editing#536.
-
w3c/clipboard-apis
-
1 issue opened.
-
readText() resolves promises while in parallel w3c/clipboard-apis#249, by @annevk.
-
-
1 pull request merged.
-
Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() w3c/clipboard-apis#248.
-
-
1 pull request received 13 new comments.
-
Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() w3c/clipboard-apis#248 (13 comments by @annevk, @dandclark, @EdgarChen, @johanneswilm, @shwetabin)
-
w3c/input-events
-
1 issue received 5 new comments.
-
`insertCompositionText` (and `isComposing`) cannot tell the input event accompanied by compositionEnd from the other WIP IME input events w3c/input-events#176 (5 comments by @johanneswilm, @michael, @ragoulik, @tats-u)
-
w3c/selection-api
-
1 issue closed.
-
1 issue received 2 new comments.
-
Remove single range restriction for selection interface apis w3c/selection-api#358 (2 comments by @johanneswilm)
-
-
1 pull request opened.
-
Multi-range selection support w3c/selection-api#359, by @sambandaru.
-
-
2 pull requests merged.
-
Fix selection.modify() to use resolved text direction instead of inline base direction w3c/selection-api#357.
-
Set "has scheduled selectionchange event" to true w3c/selection-api#356.
-
-
2 pull requests received 5 new comments.
-
Fix selection.modify() to use resolved text direction instead of inline base direction w3c/selection-api#357 (3 comments by @johanneswilm, @sambandaru)
-
Set "has scheduled selectionchange event" to true w3c/selection-api#356 (2 comments by @TimvdLippe, @w3cbot)
-
TR publications
-
1 document published.
-
Input Events Level 2 published as a Working Draft. History of Input Events Level 2
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Prashant Singh (Microsoft Corporation) joined.
-
GitHub
w3c/clipboard-apis
-
2 pull requests received 17 new comments.
-
Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() w3c/clipboard-apis#248 (16 comments by @annevk, @EdgarChen, @shwetabin)
-
w3c/clipboard-apis#132 (1 comment by @yume-chan)
-
w3c/selection-api
-
1 issue opened.
-
Remove single range restriction for selection interface apis w3c/selection-api#358, by @sambandaru.
-
-
2 pull requests received 11 new comments.
-
Fix selection.modify() to use resolved text direction instead of inline base direction w3c/selection-api#357 (10 comments by @rniwa, @sambandaru, @smaug----, @vinhill)
-
w3c/edit-context
-
2 issues opened.
-
test w3c/edit-context#131, by @dandclark.
-
Clarify how CompositionEvents should be initialized w3c/edit-context#129, by @ltenmoz.
-
-
1 issue closed.
-
test w3c/edit-context#131.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Specify what TextUpdateEvent updateRangeStart/End should be set to. w3c/edit-context#130, by @ltenmoz.
-
w3c/input-events
-
1 issue closed.
-
getTargetRanges definition for EditContext is unclear w3c/input-events#178.
-
-
1 issue received 1 new comment.
-
`insertCompositionText` (and `isComposing`) cannot tell the input event accompanied by compositionEnd from the other WIP IME input events w3c/input-events#176 (1 comment by @michael)
-
-
1 pull request merged.
-
Clarify getTargetRanges() for EditContext w3c/input-events#179.
-
-
1 pull request received 1 new comment.
-
w3c/input-events#175 (1 comment by @w3cbot)
-
w3c/editing
-
1 issue closed.
-
Charter - open tasks w3c/editing#527.
-
-
3 issues received 8 new comments.
-
Clarification on [NoInterfaceObject] for SVGPathSegment and Usage of setPathData() w3c/editing#483 (2 comments by @lovasoa, @viralipurbey)
-
Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable w3c/editing#523 (1 comment by @smaug----)
-
2 pull requests opened.
-
rm Caret Movement per Google feedback on charter poll. editing-2025.html w3c/editing#535, by @tantek.
-
restore mitigations and residual risk text. editing-2025.html w3c/editing#534, by @tantek.
-
-
1 pull request merged.
-
restore mitigations and residual risk text. editing-2025.html w3c/editing#534.
-
-
1 pull request closed.
-
2 pull requests reopened.
-
rm Caret Movement per Google feedback on charter poll. editing-2025.html w3c/editing#535, by @johanneswilm.
-
rm Caret Movement per Google feedback on charter poll. editing-2025.html w3c/editing#535, by @siusin.
-
-
1 pull request received 6 new comments.
-
rm Caret Movement per Google feedback on charter poll. editing-2025.html w3c/editing#535 (6 comments by @johanneswilm, @jyasskin, @siusin, @tantek)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 2 July 2026.
-
TR publications
-
1 document published.
-
EditContext API published as a Working Draft. History of EditContext API
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Cybozu W3C (Cybozu) joined.
-
Koki Kosaki (Cybozu) joined.
-
John An (Microsoft Corporation) joined.
-
-
1 organization joined.
-
Cybozu joined.
-
GitHub
w3c/edit-context
-
2 issues opened.
-
Improve timing for Update the Text Edit Context w3c/edit-context#127, by @ltenmoz.
-
-
1 issue received 1 new comment.
-
5 pull requests opened.
-
Clarify `updateText` behavior when rangeStart > rangeEnd w3c/edit-context#128, by @ltenmoz.
-
Turn off `VALIDATE_LINKS` (temporarily?) to fix CI w3c/edit-context#126, by @ltenmoz.
-
Add default values to `*Init` dictionaries w3c/edit-context#125, by @ltenmoz.
-
Clean up deactivating EditContext w3c/edit-context#123, by @ltenmoz.
-
Remove `compositionStart`/`End` from TextUpdateEventInit. w3c/edit-context#122, by @ltenmoz.
-
-
2 pull requests merged.
-
Turn off `VALIDATE_LINKS` (temporarily?) to fix CI w3c/edit-context#126.
-
Clarify `updateText` behavior when rangeStart > rangeEnd w3c/edit-context#128.
-
-
4 pull requests received 5 new comments.
-
Remove `compositionStart`/`End` from TextUpdateEventInit. w3c/edit-context#122 (1 comment by @smaug----)
w3c/input-events
-
2 issues opened.
-
How can developers handle platform specific shortcuts for caret navigation? w3c/input-events#180, by @flackr.
-
getTargetRanges definition for EditContext is unclear w3c/input-events#178, by @ltenmoz.
-
-
2 issues received 6 new comments.
-
getTargetRanges definition for EditContext is unclear w3c/input-events#178 (3 comments by @dandclark, @johanneswilm, @ltenmoz)
-
-
1 pull request opened.
-
Clarify getTargetRanges() for EditContext w3c/input-events#179, by @ltenmoz.
-
w3c/selection-api
-
2 pull requests opened.
-
Fix selection.modify() to use resolved text direction instead of inline base direction w3c/selection-api#357, by @sambandaru.
-
Set "has scheduled selectionchange event" to true w3c/selection-api#356, by @TimvdLippe.
-
-
2 pull requests received 7 new comments.
-
Fix selection.modify() to use resolved text direction instead of inline base direction w3c/selection-api#357 (5 comments by @dandclark, @sambandaru)
-
Set "has scheduled selectionchange event" to true w3c/selection-api#356 (2 comments by @annevk, @TimvdLippe)
-
w3c/editing
-
2 issues opened.
-
Caret movement based on visual screen position rather than DOM order? w3c/editing#533, by @michael.
-
-
1 issue closed.
-
6 issues received 6 new comments.
-
Caret movement based on visual screen position rather than DOM order? w3c/editing#533 (1 comment by @michael)
-
Safari: `height: 100%` changes layout when the parent height is defined via `aspect-ratio` w3c/editing#531 (1 comment by @michael)
-
Spec: Empty addressable content fields with placeholders w3c/editing#528 (1 comment by @johanneswilm)
-
Firefox: event.getTargetRanges() in beforeinput not consistent with window.getSelection() w3c/editing#493 (1 comment by @michael)
-
execCommand commands listed in MDN but not in the spec w3c/editing#530 (1 comment by @masayuki-nakano)
-
-
1 pull request opened.
-
Repro for #531 w3c/editing#532, by @michael.
-
-
1 pull request closed.
-
Repro for #531 w3c/editing#532.
-
-
1 pull request received 1 new comment.
w3c/clipboard-apis
-
1 pull request received 2 new comments.
-
Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() w3c/clipboard-apis#248 (2 comments by @annevk, @siusin)
-
Past meetings
-
1 meeting.
Participants
-
1 participant left.
-
Howard Edwards (Bocoup) left.
-
GitHub
w3c/editing
-
3 issues opened.
-
execCommand commands listed in MDN but not in the spec w3c/editing#530, by @zcorpan.
-
Explainer for Caret Movement Spec w3c/editing#529, by @johanneswilm.
-
Spec: Empty addressable content fields with placeholders w3c/editing#528, by @michael.
-
-
5 issues received 7 new comments.
-
Spec: Empty addressable content fields with placeholders w3c/editing#528 (2 comments by @johanneswilm, @siusin)
-
Firefox: event.getTargetRanges() in beforeinput not consistent with window.getSelection() w3c/editing#493 (1 comment by @smaug----)
-
Safari Desktop: Adding an empty span to an otherwise empty editable element, makes the element unselectable w3c/editing#516 (1 comment by @johanneswilm)
-
Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable w3c/editing#523 (1 comment by @johanneswilm)
-
1 pull request merged.
-
add a draft charter for the 2025 recharter w3c/editing#515.
-
w3c/edit-context
-
2 issues opened.
-
How to make Context Menu show the EditContext selection instead of the canvas items w3c/edit-context#121, by @ApoloApps.
-
Should multiple selection ranges be supported? w3c/edit-context#120, by @12joan.
-
w3c/clipboard-apis
-
3 issues received 4 new comments.
-
Standardize Clipboard Source url, aka the URL from which the content has been copied from w3c/clipboard-apis#244 (1 comment by @johanneswilm)
-
1 pull request opened.
-
Defer OS clipboard read from clipboard.read() to ClipboardItem.getType() w3c/clipboard-apis#248, by @shwetabin.
-
w3c/input-events
-
2 issues closed.
-
Encourage browsers to include files in `beforeinput` DataTransfer event w3c/input-events#120.
-
3 issues received 9 new comments.
-
input-events-spin-button-click-on-number-input-delete-document.html expects undefined thing w3c/input-events#177 (6 comments by @annevk, @johanneswilm, @masayuki-nakano, @utpathak, @whimboo)
-
`insertCompositionText` (and `isComposing`) cannot tell the input event accompanied by compositionEnd from the other WIP IME input events w3c/input-events#176 (2 comments by @johanneswilm, @smaug----)
-
Gather informations on content replaced by insertReplacementText or trigger a deleteByReplacement event? w3c/input-events#133 (1 comment by @whereswaldon)
-
Past meetings
-
1 meeting.
GitHub
w3c/editing
-
3 issues opened.
-
Charter - open tasks w3c/editing#527, by @johanneswilm.
-
Spec proposal for document.execCommand(‘insertHTML’) w3c/editing#525, by @shwetabin.
-
-
1 issue closed.
-
2025 May meeting cancelled w3c/editing#485.
-
-
2 issues received 2 new comments.
-
Spec proposal for document.execCommand(‘insertHTML’) w3c/editing#525 (1 comment by @masayuki-nakano)
-
1 pull request merged.
-
Repro for #523. w3c/editing#524.
-
w3c/input-events
-
2 issues received 2 new comments.
-
input-events-spin-button-click-on-number-input-delete-document.html expects undefined thing w3c/input-events#177 (1 comment by @johanneswilm)
-
w3c/selection-api
-
1 issue received 1 new comment.
-
w3c/selection-api#99 (1 comment by @masayuki-nakano)
-
Past meetings
-
1 meeting.
GitHub
w3c/clipboard-apis
-
1 issue opened.
-
Clipboarding and Multipart MIME w3c/clipboard-apis#247, by @AdamSobieski.
-
-
2 issues received 4 new comments.
-
Selective Clipboard Format Read w3c/clipboard-apis#240 (3 comments by @css-meeting-bot, @EdgarChen, @roraja)
-
w3c/selection-api
-
3 issues opened.
-
Inconsistent selectstart event timing and prevention capability w3c/selection-api#355, by @flackr.
-
the steps of `Selection.setBaseAndExtent()` do not check the node type w3c/selection-api#354, by @masayuki-nakano.
-
-
1 issue received 1 new comment.
-
the steps of Selection.extend() does not check whether the given offset is valid in the container w3c/selection-api#353 (1 comment by @masayuki-nakano)
-
w3c/editing
-
3 issues opened.
-
[execCommand] Incorrect condition in 9.9 toggle-lists w3c/editing#521, by @InvalidUsernameException.
-
2 issues received 4 new comments.
-
Firefox: Up/Down arrow navigation doesn't work with absolutely positioned elements in contenteditable w3c/editing#523 (3 comments by @masayuki-nakano, @michael)
-
`insertText` should move to parent node if range's start container is a void element w3c/editing#522 (1 comment by @masayuki-nakano)
-
-
1 pull request opened.
-
Repro for #523. w3c/editing#524, by @michael.
-
w3c/input-events
-
2 issues received 5 new comments.
-
input-events-spin-button-click-on-number-input-delete-document.html expects undefined thing w3c/input-events#177 (4 comments by @johanneswilm, @whimboo)
-