Web Editing Working Group - Activity in 2023
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/virtual-keyboard
-
1 issue opened.
w3c/editing
-
2 issues received 13 new comments.
-
Delayed clipboard rendering API shape. w3c/editing#423 (8 comments by @saschanaz, @snianu, @tilgovi)
-
[Delayed Clipboard Rendering] Privacy issue while reading data for web custom types w3c/editing#439 (5 comments by @evanstade, @johanneswilm, @smaug----, @snianu)
-
-
1 pull request opened.
-
Don't enable execCommand commands in EditContext w3c/editing#457, by @dandclark.
-
-
1 pull request merged.
-
Don't enable execCommand commands in EditContext w3c/editing#457.
-
-
1 pull request received 1 new comment.
w3c/clipboard-apis
-
7 issues opened.
-
Merge a PR only with explicit implementor consensus (followup) w3c/clipboard-apis#207, by @saschanaz.
-
Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization w3c/clipboard-apis#206, by @snianu.
-
References to permissions w3c/clipboard-apis#205, by @evanstade.
-
algorithms don't enforce focus requirement w3c/clipboard-apis#203, by @evanstade.
-
Parallelism and task sources w3c/clipboard-apis#202, by @evanstade.
-
Feature detection of web custom format support w3c/clipboard-apis#201, by @DavidMulder0.
-
-
2 issues closed.
-
Aljbore w3c/clipboard-apis#204.
-
Feature detection of web custom format support w3c/clipboard-apis#201.
-
-
6 issues received 11 new comments.
-
Merge a PR only with explicit implementor consensus (followup) w3c/clipboard-apis#207 (4 comments by @annevk, @snianu, @zcorpan)
-
Read Blob data for the supported formats on-demand during getType. w3c/clipboard-apis#191 (2 comments by @evanstade, @snianu)
-
Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization w3c/clipboard-apis#206 (1 comment by @snianu)
-
-
1 pull request opened.
-
Add non-normative and optional texts. w3c/clipboard-apis#208, by @snianu.
-
-
2 pull requests received 21 new comments.
-
Add `unsanitized` option to async clipboard API. w3c/clipboard-apis#197 (12 comments by @saschanaz, @snianu)
-
Add non-normative and optional texts. w3c/clipboard-apis#208 (9 comments by @EdgarChen, @sanketj, @snianu)
-
w3c/input-events
-
1 issue closed.
-
allow you to specify targetRanges and dataTransfer in InputEventInit w3c/input-events#147.
-
-
1 issue received 3 new comments.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (3 comments by @dandclark, @johanneswilm, @sanketj)
-
-
2 pull requests opened.
-
Update intention for insertReplacementText to include writing suggestions w3c/input-events#149, by @sanketj.
-
make code point replacement normative, based on resolution on #146 w3c/input-events#148, by @johanneswilm.
-
-
1 pull request merged.
-
make code point replacement normative, based on resolution on #146 w3c/input-events#148.
-
w3c/edit-context
-
1 issue opened.
-
Handling 'backwards' selection direction in an EditContext implementation w3c/edit-context#81, by @GaurangTandon.
-
-
3 issues closed.
-
Which coordinate system should be used? w3c/edit-context#39.
-
-
1 issue received 1 new comment.
-
Handling 'backwards' selection direction in an EditContext implementation w3c/edit-context#81 (1 comment by @dandclark)
-
-
4 pull requests opened.
-
Add client coordinate definition and note on usage during scroll w3c/edit-context#85, by @dandclark.
-
Remove codepoint locations struct w3c/edit-context#84, by @dandclark.
-
Clarify designMode corner case w3c/edit-context#83, by @dandclark.
-
Remove secure context requirement w3c/edit-context#82, by @dandclark.
-
-
4 pull requests merged.
-
Add client coordinate definition and note on usage during scroll w3c/edit-context#85.
-
Remove codepoint locations struct w3c/edit-context#84.
-
Clarify designMode corner case w3c/edit-context#83.
-
Remove secure context requirement w3c/edit-context#82.
-
-
3 pull requests received 20 new comments.
-
Add client coordinate definition and note on usage during scroll w3c/edit-context#85 (13 comments by @dandclark, @snianu)
-
w3c/selection-api
-
1 issue opened.
-
Need spec changes to Range and StaticRange to support nodes in different tree? w3c/selection-api#169, by @sefeng211.
-
-
1 issue received 1 new comment.
-
Need spec changes to Range and StaticRange to support nodes in different tree? w3c/selection-api#169 (1 comment by @annevk)
-
Past meetings
-
1 meeting.
GitHub
w3c/editing
-
1 issue closed.
-
Linked privacy security doc is for older pickling proposal? w3c/editing#452.
-
-
1 issue received 10 new comments.
-
[Delayed Clipboard Rendering] Privacy issue while reading data for web custom types w3c/editing#439 (10 comments by @johanneswilm, @smaug----, @snianu)
-
-
1 pull request merged.
-
Remove write and add more details on read. w3c/editing#456.
-
w3c/clipboard-apis
-
2 issues opened.
-
Optional data types description seems wrong w3c/clipboard-apis#200, by @annevk.
-
-
1 issue closed.
-
Should reading the clipboard throw DataError or empty clipboard items? w3c/clipboard-apis#179.
-
-
6 issues received 11 new comments.
-
Read Blob data for the supported formats on-demand during getType. w3c/clipboard-apis#191 (2 comments by @evanstade, @snianu)
-
Should reading the clipboard throw DataError or empty clipboard items? w3c/clipboard-apis#179 (2 comments by @snianu)
-
Add method `match` (`clipboard.match(regex)`) to check clipboard for pattern matching before reading - as it is done in iOS w3c/clipboard-apis#199 (1 comment by @ErmachenkoBoris)
-
w3c/clipboard-apis#92 (1 comment by @sanketj)
-
1 pull request opened.
-
Allow empty ClipboardItem. w3c/clipboard-apis#198, by @snianu.
-
-
1 pull request merged.
-
Add `unsanitized` option to async clipboard API. w3c/clipboard-apis#197.
-
-
1 pull request closed.
-
Allow empty ClipboardItem. w3c/clipboard-apis#198.
-
-
2 pull requests received 58 new comments.
-
Add `unsanitized` option to async clipboard API. w3c/clipboard-apis#197 (53 comments by @evanstade, @sanketj, @snianu, @zcorpan)
-
w3c/input-events
-
1 issue opened.
-
allow you to specify targetRanges and dataTransfer in InputEventInit w3c/input-events#147, by @johanneswilm.
-
-
1 issue closed.
-
Adjustments for EditContext w3c/input-events#143.
-
-
2 issues received 6 new comments.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (5 comments by @Comandeer, @dandclark, @johanneswilm)
-
allow you to specify targetRanges and dataTransfer in InputEventInit w3c/input-events#147 (1 comment by @johanneswilm)
-
-
1 pull request merged.
-
Changes for EditContext w3c/input-events#145.
-
-
1 pull request received 2 new comments.
w3c/edit-context
-
1 issue closed.
-
Fix the Status section w3c/edit-context#79.
-
-
3 issues received 5 new comments.
-
Can EditContext works as normally even in designMode if set to the documentElement and/or body? w3c/edit-context#74 (2 comments by @dandclark, @smaug----)
-
-
1 pull request opened.
-
Add Dan as Editor w3c/edit-context#80, by @dandclark.
-
-
1 pull request merged.
-
Add Dan as Editor w3c/edit-context#80.
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
TIEN MAI (Microsoft Corporation) joined.
-
GitHub
w3c/editing
-
2 issues opened.
-
Linked privacy security doc is for older pickling proposal? w3c/editing#452, by @caraitto.
-
1 issue closed.
-
TPAC 2023 agenda w3c/editing#438.
-
-
1 issue received 1 new comment.
-
5 pull requests opened.
-
Remove write and add more details on read. w3c/editing#456, by @snianu.
-
Add privacy-security doc. w3c/editing#454, by @snianu.
-
Add example for read unsanitized option. w3c/editing#453, by @snianu.
-
Clarify the exception text. w3c/editing#445, by @snianu.
-
Add exceptions in read method. w3c/editing#444, by @snianu.
-
-
5 pull requests merged.
-
Add privacy-security doc. w3c/editing#454.
-
Update explainer to add the new write algorithm. w3c/editing#436.
-
Add example for read unsanitized option. w3c/editing#453.
-
Clarify the exception text. w3c/editing#445.
-
Add exceptions in read method. w3c/editing#444.
-
-
4 pull requests received 48 new comments.
w3c/clipboard-apis
-
4 issues received 9 new comments.
-
Feature detection for supported clipboard formats w3c/clipboard-apis#170 (2 comments by @snianu, @yisibl)
-
Read Blob data for the supported formats on-demand during getType. w3c/clipboard-apis#191 (1 comment by @snianu)
-
Start and End fragment tags in text/html format on Windows w3c/clipboard-apis#193 (1 comment by @css-meeting-bot)
-
1 pull request opened.
-
Add `unsanitized` option to async clipboard API. w3c/clipboard-apis#197, by @snianu.
-
-
1 pull request merged.
-
Add 'starts with' to web custom format prefix. w3c/clipboard-apis#195.
-
-
3 pull requests received 33 new comments.
-
Add 'starts with' to web custom format prefix. w3c/clipboard-apis#195 (14 comments by @evanstade, @snianu)
-
Add `unsanitized` option to async clipboard API. w3c/clipboard-apis#197 (11 comments by @sanketj, @snianu, @yisibl)
-
Add supports API for async clipboard. w3c/clipboard-apis#192 (8 comments by @css-meeting-bot, @evanstade, @inexorabletash, @snianu, @tomayac)
-
w3c/edit-context
-
7 issues opened.
-
Fix the Status section w3c/edit-context#79, by @jyasskin.
-
Clarify `contenteditable="false"` elements which is associated with an `EditContext` w3c/edit-context#70, by @masayuki-nakano.
-
Does the composition range need to be exposed on EditContext/TextUpdate? w3c/edit-context#69, by @dandclark.
-
-
10 issues closed.
-
Custom spellchecking w3c/edit-context#5.
-
`editContext` is on HTMLElement but `attachedElements()` returns Element. w3c/edit-context#68.
-
Does the composition range need to be exposed on EditContext/TextUpdate? w3c/edit-context#69.
-
Some thoughts on accessibility w3c/edit-context#6.
-
EditContext: how is bold represented? w3c/edit-context#17.
-
EditContext: Who's going to handle caret navigation? w3c/edit-context#2.
-
EditContext: processing model w3c/edit-context#23.
-
"text state" updated from in parallel but also API accessible w3c/edit-context#41.
-
-
16 issues received 31 new comments.
-
`Document.execCommand`, `Document.queryCommandValue`, `Document.queryCommandState`, `Document.queryCommandEnabled`, `Document.queryCommandSupported`, `Document.queryCommandIndeterm` behavior when an EditContext editing host has focus w3c/edit-context#71 (9 comments by @dandclark, @johanneswilm, @masayuki-nakano)
-
Can EditContext works as normally even in designMode if set to the documentElement and/or body? w3c/edit-context#74 (4 comments by @dandclark, @johanneswilm, @masayuki-nakano)
-
Would it be useful to have an activeEditContext property on document? w3c/edit-context#4 (2 comments by @gdh1995)
-
EditContext spec should define composition events as they are (not?) fired on EditContext editing host w3c/edit-context#72 (2 comments by @dandclark, @johanneswilm)
-
Should the methods of EditContext throw an exception if they abort due to not activated? w3c/edit-context#26 (2 comments by @dandclark)
-
Does the composition range need to be exposed on EditContext/TextUpdate? w3c/edit-context#69 (2 comments by @dandclark)
-
EditContext has compositionRange(Start|End) but TextUpdateEvent has composition(Start|End) w3c/edit-context#27 (1 comment by @dandclark)
-
Clarify `contenteditable="false"` elements which is associated with an `EditContext` w3c/edit-context#70 (1 comment by @dandclark)
-
The timing of "deactivate an EditContext" when `HTMLElement.editContext` is replaced with another one or `null` w3c/edit-context#75 (1 comment by @dandclark)
-
`editContext` is on HTMLElement but `attachedElements()` returns Element. w3c/edit-context#68 (1 comment by @dandclark)
-
w3c/edit-context#2 (1 comment by @dandclark)
-
"text state" updated from in parallel but also API accessible w3c/edit-context#41 (1 comment by @dandclark)
-
-
3 pull requests opened.
-
Update security-privacy.md w3c/edit-context#78, by @dandclark.
-
Remove 'is active' checks from EditContext setters w3c/edit-context#77, by @dandclark.
-
Change attachedElements() to return list of HTMLElement w3c/edit-context#76, by @dandclark.
-
-
4 pull requests merged.
-
Update security-privacy.md w3c/edit-context#78.
-
Remove 'is active' checks from EditContext setters w3c/edit-context#77.
-
Change attachedElements() to return list of HTMLElement w3c/edit-context#76.
-
Remove unnecessary getters on EditContext and TextUpdateEvent w3c/edit-context#58.
-
w3c/input-events
-
1 issue opened.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146, by @masayuki-nakano.
-
-
1 issue received 13 new comments.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (13 comments by @dandclark, @johanneswilm, @masayuki-nakano)
-
Lifecycle
-
1 charter started.
-
Chartered until 26 September 2025.
-
TR publications
-
1 document published.
-
Input Events Level 1 published as a Discontinued Draft. History of Input Events Level 1
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Michael Jackson (Microsoft Corporation) joined.
-
Jan Jaeschke (Mozilla Foundation) joined.
-
GitHub
w3c/edit-context
-
1 issue opened.
-
`editContext` is on HTMLElement but `attachedElements()` returns Element. w3c/edit-context#68, by @dandclark.
-
-
5 issues closed.
-
The `compositionend` event is no longer fired w3c/edit-context#34.
-
Should attachedElements() return elements that aren't in the DOM? w3c/edit-context#59.
-
Should TextFormat.underlineStyle be an enum? w3c/edit-context#55.
-
EditContext: "is activated" is not defined w3c/edit-context#20.
-
Secure context for EditContext? w3c/edit-context#11.
-
-
7 issues received 8 new comments.
-
`editContext` is on HTMLElement but `attachedElements()` returns Element. w3c/edit-context#68 (1 comment by @annevk)
-
Should attachedElements() return elements that aren't in the DOM? w3c/edit-context#59 (1 comment by @dandclark)
-
"text state" updated from in parallel but also API accessible w3c/edit-context#41 (1 comment by @dandclark)
-
7 pull requests opened.
-
Add entrypoint for input-events spec w3c/edit-context#67, by @dandclark.
-
Fix compositionend links w3c/edit-context#66, by @dandclark.
-
Replace attachedElements() issue with note on lifetime w3c/edit-context#65, by @dandclark.
-
Make underlineStyle and underlineThickness enums w3c/edit-context#64, by @dandclark.
-
Fix link to compositionend event w3c/edit-context#63, by @dontcallmedom.
-
Complete missing parts of 'Update the EditContext' w3c/edit-context#62, by @dandclark.
-
Update Activation and Deactivation behaviors w3c/edit-context#61, by @dandclark.
-
-
7 pull requests merged.
-
Add entrypoint for input-events spec w3c/edit-context#67.
-
Fix compositionend links w3c/edit-context#66.
-
Fix link to compositionend event w3c/edit-context#63.
-
Complete missing parts of 'Update the EditContext' w3c/edit-context#62.
-
Replace attachedElements() issue with note on lifetime w3c/edit-context#65.
-
Make underlineStyle and underlineThickness enums w3c/edit-context#64.
-
Update Activation and Deactivation behaviors w3c/edit-context#61.
-
-
2 pull requests received 3 new comments.
-
Replace attachedElements() issue with note on lifetime w3c/edit-context#65 (2 comments by @dandclark, @snianu)
-
w3c/editing
-
5 issues opened.
-
TPAC 2023 agenda w3c/editing#438, by @johanneswilm.
-
2 issues closed.
-
TPAC 2023 participation - Call for topics w3c/editing#427.
-
5 issues received 18 new comments.
-
RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors w3c/editing#437 (9 comments by @joanmarie, @johanneswilm, @zcorpan)
-
[Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? w3c/editing#424 (3 comments by @snianu)
-
[Delayed Clipboard Rendering] Privacy issue while reading data for web custom types w3c/editing#439 (3 comments by @annevk, @snianu)
-
Define behavior of pressing enter in inline editing host w3c/editing#430 (1 comment by @johanneswilm)
-
-
2 pull requests opened.
-
add 'all known' to the Success Criteria section of the proposed charter w3c/editing#441, by @siusin.
-
be more precise about out of scope w3c/editing#440, by @siusin.
-
-
2 pull requests merged.
-
be more precise about out of scope w3c/editing#440.
-
3 pull requests received 5 new comments.
-
add 'all known' to the Success Criteria section of the proposed charter w3c/editing#441 (2 comments by @siusin)
-
Update explainer to add the new write algorithm. w3c/editing#436 (2 comments by @johanneswilm, @snianu)
-
w3c/clipboard-apis
-
2 issues opened.
-
Start and End fragment tags in text/html format on Windows w3c/clipboard-apis#193, by @snianu.
-
Read Blob data for the supported formats on-demand during getType. w3c/clipboard-apis#191, by @snianu.
-
-
2 issues closed.
-
Arbitrary clipboard types w3c/clipboard-apis#165.
-
Feature detection for supported clipboard formats w3c/clipboard-apis#170.
-
-
4 issues received 7 new comments.
-
Feature detection for supported clipboard formats w3c/clipboard-apis#170 (2 comments by @martinthomson, @snianu)
-
w3c/clipboard-apis#141 (2 comments by @polx)
-
Read Blob data for the supported formats on-demand during getType. w3c/clipboard-apis#191 (1 comment by @inexorabletash)
-
-
4 pull requests opened.
-
Scope events to GlobalEventHandlers w3c/clipboard-apis#196, by @dontcallmedom.
-
Add 'starts with' to web custom format prefix. w3c/clipboard-apis#195, by @snianu.
-
Update custom types on Mac. w3c/clipboard-apis#194, by @snianu.
-
Add supports API for async clipboard. w3c/clipboard-apis#192, by @snianu.
-
-
5 pull requests merged.
-
Scope events to GlobalEventHandlers w3c/clipboard-apis#196.
-
Update custom types on Mac. w3c/clipboard-apis#194.
-
Add Web Custom format w3c/clipboard-apis#175.
-
Add supports API for async clipboard. w3c/clipboard-apis#192.
-
Async clipboard api - write api example: resolved error w3c/clipboard-apis#189.
-
-
4 pull requests received 20 new comments.
-
Add supports API for async clipboard. w3c/clipboard-apis#192 (11 comments by @evanstade, @saschanaz, @snianu)
-
w3c/input-events
-
2 issues opened.
-
Definitions for 'Update the DOM'/'Update the DOM element' w3c/input-events#144, by @dandclark.
-
Adjustments for EditContext w3c/input-events#143, by @johanneswilm.
-
-
2 issues closed.
-
Definitions for 'Update the DOM'/'Update the DOM element' w3c/input-events#144.
-
"character" is not defined w3c/input-events#73.
-
-
2 issues received 7 new comments.
-
Definitions for 'Update the DOM'/'Update the DOM element' w3c/input-events#144 (2 comments by @dandclark, @johanneswilm)
-
1 pull request opened.
-
Changes for EditContext w3c/input-events#145, by @dandclark.
-
-
4 pull requests merged.
-
link to grapheme definition in i18n-glossary, fixes #73 w3c/input-events#139.
-
Adjust difference between level 1 and 2 w3c/input-events#142.
-
chore: enable auto-publish w3c/input-events#118.
-
remove/fix links to comply with respec w3c/input-events#138.
-
-
1 pull request received 1 new comment.
w3c/selection-api
-
2 issues opened.
-
Specify the behavior when DOM mutation occurs across shadow-crossing selection w3c/selection-api#168, by @rniwa.
-
getSelection().addRange should allow range with both boundary points in shadow tree w3c/selection-api#167, by @rniwa.
-
-
2 issues received 6 new comments.
-
Specify the behavior when DOM mutation occurs across shadow-crossing selection w3c/selection-api#168 (4 comments by @annevk, @mfreed7, @smaug----)
-
Define `Selection.rangeCount` when an input field is focused w3c/selection-api#166 (2 comments by @annevk, @smaug----)
-
w3c/virtual-keyboard
-
1 issue closed.
-
Question: API isn't accessible in unsecure context? w3c/virtual-keyboard#20.
-
Past meetings
Participants
-
1 participant left.
-
liejin huang (W3C Invited Experts) left.
-
GitHub
w3c/editing
-
1 issue closed.
-
[charter] execCommand spec should be in scope w3c/editing#432.
-
-
1 pull request opened.
-
Update explainer to add the new write algorithm. w3c/editing#436, by @snianu.
-
w3c/edit-context
-
1 issue opened.
-
Should attachedElements() return elements that aren't in the DOM? w3c/edit-context#59, by @dandclark.
-
-
8 issues closed.
-
Should EditContext be associated with a Node representing the "view"? w3c/edit-context#7.
-
inputMode property of EditContext w3c/edit-context#3.
-
EditContext: Do IME see the plaintext in `EditContext`? w3c/edit-context#9.
-
EditContext: If nested elements attached by `EditContext`, what happens? w3c/edit-context#13.
-
Event firing and editability for nested editable elements w3c/edit-context#53.
-
What happens when an editing host is associated with an EditContext? w3c/edit-context#38.
-
-
11 issues received 14 new comments.
-
Event firing and editability for nested editable elements w3c/edit-context#53 (2 comments by @dandclark)
-
What happens when an editing host is associated with an EditContext? w3c/edit-context#38 (2 comments by @dandclark)
-
Should attachedElements() return elements that aren't in the DOM? w3c/edit-context#59 (1 comment by @dandclark)
-
w3c/edit-context#7 (1 comment by @dandclark)
-
EditContext: Should `selectionStart` and `selectionEnd` be upadeted when `updateText()` is called? w3c/edit-context#10 (1 comment by @dandclark)
-
EditContext: Do IME see the plaintext in `EditContext`? w3c/edit-context#9 (1 comment by @dandclark)
-
EditContext: If nested elements attached by `EditContext`, what happens? w3c/edit-context#13 (1 comment by @dandclark)
-
EditContext: Should throw exception when `Element.editContext` is set to specific elements? w3c/edit-context#14 (1 comment by @dandclark)
-
4 pull requests opened.
-
Clarify active EditContext behavior w3c/edit-context#60, by @dandclark.
-
Remove unnecessary getters on EditContext and TextUpdateEvent w3c/edit-context#58, by @dandclark.
-
Remove TextFormat colors w3c/edit-context#57, by @dandclark.
-
Clarify behaviors around conflicts with contenteditable w3c/edit-context#56, by @dandclark.
-
-
3 pull requests merged.
-
Clarify active EditContext behavior w3c/edit-context#60.
-
Remove TextFormat colors w3c/edit-context#57.
-
Clarify behaviors around conflicts with contenteditable w3c/edit-context#56.
-
-
1 pull request received 8 new comments.
w3c/clipboard-apis
-
1 issue opened.
-
Async Clipboard API take more time compared to DataTransfer API to read/write data in System Clipboard w3c/clipboard-apis#190, by @amitavak.
-
-
1 issue closed.
-
1 issue received 1 new comment.
-
Async Clipboard API take more time compared to DataTransfer API to read/write data in System Clipboard w3c/clipboard-apis#190 (1 comment by @snianu)
-
w3c/selection-api
-
1 issue opened.
-
Define `Selection.rangeCount` when an input field is focused w3c/selection-api#166, by @whsieh.
-
GitHub
w3c/edit-context
-
2 issues opened.
-
Should TextFormat.underlineStyle be an enum? w3c/edit-context#55, by @dandclark.
-
Should we add TextFormat.textColor back? w3c/edit-context#54, by @dandclark.
-
-
2 issues received 10 new comments.
-
What happens when an editing host is associated with an EditContext? w3c/edit-context#38 (7 comments by @dandclark, @johanneswilm)
-
Event firing and editability for nested editable elements w3c/edit-context#53 (3 comments by @dandclark, @johanneswilm)
-
w3c/virtual-keyboard
-
1 issue opened.
-
Where is the dispatch of geometrychange events defined? w3c/virtual-keyboard#21, by @birtles.
-
w3c/editing
-
1 issue received 3 new comments.
-
Define behavior of pressing enter in inline editing host w3c/editing#430 (3 comments by @chrishtr, @masayuki-nakano)
-
w3c/selection-api
-
1 issue received 3 new comments.
Past meetings
GitHub
w3c/editing
-
2 issues opened.
-
CfC to include execCommand to list of possible deliverables w3c/editing#435, by @johanneswilm.
-
[charter] execCommand spec should be in scope w3c/editing#432, by @zcorpan.
-
-
2 issues closed.
-
Should contenteditable=plaintext-only be standardized? w3c/editing#162.
-
CfC to include execCommand to list of possible deliverables w3c/editing#435.
-
-
8 issues received 29 new comments.
-
[charter] execCommand spec should be in scope w3c/editing#432 (19 comments by @annevk, @chrishtr, @hober, @johanneswilm, @zcorpan)
-
Behavior of insert* commands for contenteditable=plaintext-only w3c/editing#419 (3 comments by @kojiishi, @masayuki-nakano, @zcorpan)
-
Define behavior of pressing enter in inline editing host w3c/editing#430 (2 comments by @chrishtr, @masayuki-nakano)
-
w3c/editing#162 (1 comment by @zcorpan)
-
[Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? w3c/editing#424 (1 comment by @snianu)
-
-
2 pull requests opened.
-
execCommand as a potential deliverable w3c/editing#434, by @siusin.
-
add 2023 draft charter w3c/editing#433, by @siusin.
-
-
2 pull requests merged.
-
execCommand as a potential deliverable w3c/editing#434.
-
add 2023 draft charter w3c/editing#433.
-
-
2 pull requests received 7 new comments.
w3c/edit-context
-
2 issues opened.
-
Event firing and editability for nested editable elements w3c/edit-context#53, by @dandclark.
-
Should an EditContext be able to have multiple associated elements? w3c/edit-context#50, by @dandclark.
-
-
2 issues closed.
-
Should an EditContext be able to have multiple associated elements? w3c/edit-context#50.
-
Clarify association between elements and EditContext w3c/edit-context#40.
-
-
2 issues reopened.
-
Which coordinate system should be used? w3c/edit-context#39, by @dandclark.
-
Should an EditContext be able to have multiple associated elements? w3c/edit-context#50, by @dandclark.
-
-
3 issues received 4 new comments.
-
Should an EditContext be able to have multiple associated elements? w3c/edit-context#50 (1 comment by @dandclark)
-
3 pull requests opened.
-
Remove issue about multiple associated elements w3c/edit-context#52, by @dandclark.
-
Scope 'non-normative' header to individual sections in Introduction w3c/edit-context#51, by @dandclark.
-
Clarify editing host behaviors w3c/edit-context#49, by @dandclark.
-
-
4 pull requests merged.
-
Remove issue about multiple associated elements w3c/edit-context#52.
-
Scope 'non-normative' header to individual sections in Introduction w3c/edit-context#51.
-
Clarify editing host behaviors w3c/edit-context#49.
-
Define the concept of an EditContext's 'associated element' w3c/edit-context#48.
-
-
1 pull request received 5 new comments.
-
Define the concept of an EditContext's 'associated element' w3c/edit-context#48 (5 comments by @alexkeng, @dandclark)
-
w3c/clipboard-apis
-
1 issue received 1 new comment.
-
w3c/clipboard-apis#140 (1 comment by @ShahriarNasseri)
-
-
1 pull request opened.
-
Async clipboard api - write api example: resolved error w3c/clipboard-apis#189, by @t-trafer.
-
-
1 pull request received 1 new comment.
-
Async clipboard api - write api example: resolved error w3c/clipboard-apis#189 (1 comment by @w3cbot)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 9 September 2023.
-
TR publications
-
3 documents published.
-
Clipboard API and events published as a Working Draft. History of Clipboard API and events
-
Input Events Level 2 published as a Working Draft. History of Input Events Level 2
-
Selection API published as a Working Draft. History of Selection API
-
Past meetings
GitHub
w3c/edit-context
-
6 issues opened.
-
Event dispatch is rather hand-wavy w3c/edit-context#42, by @annevk.
-
"text state" updated from in parallel but also API accessible w3c/edit-context#41, by @annevk.
-
Clarify association between elements and EditContext w3c/edit-context#40, by @dandclark.
-
Which coordinate system should be used? w3c/edit-context#39, by @dandclark.
-
What happens when an editing host is associated with an EditContext? w3c/edit-context#38, by @dandclark.
-
-
5 issues closed.
-
Event dispatch is rather hand-wavy w3c/edit-context#42.
-
EditContext: supported element list seems somewhat arbitrary w3c/edit-context#19.
-
EditContext: define internal model w3c/edit-context#22.
-
EditContext: "it is focusable" is underdefined w3c/edit-context#21.
-
-
1 issue reopened.
-
"text state" updated from in parallel but also API accessible w3c/edit-context#41, by @dandclark.
-
-
8 issues received 29 new comments.
-
EditContext: supported element list seems somewhat arbitrary w3c/edit-context#19 (10 comments by @annevk, @bathos, @dandclark)
-
"text state" updated from in parallel but also API accessible w3c/edit-context#41 (6 comments by @annevk, @dandclark)
-
Should it be required to call updateCharacterBounds() synchronously in the characterboundsupdate event handler? w3c/edit-context#36 (3 comments by @chrishtr, @dandclark, @masayuki-nakano)
-
EditContext: "it is focusable" is underdefined w3c/edit-context#21 (3 comments by @annevk, @dandclark)
-
Clarify association between elements and EditContext w3c/edit-context#40 (1 comment by @masayuki-nakano)
-
-
7 pull requests opened.
-
Define the concept of an EditContext's 'associated element' w3c/edit-context#48, by @dandclark.
-
Fix event firing to match arguments expected by `fire an event` w3c/edit-context#47, by @dandclark.
-
Update TextUpdateEventInit field names w3c/edit-context#46, by @dandclark.
-
Remove mention of 'parallel' from 'Update the Text Edit Context' w3c/edit-context#45, by @dandclark.
-
Update supported elements w3c/edit-context#44, by @dandclark.
-
Expand events section and clarify that updateCharacterBounds can be async w3c/edit-context#43, by @dandclark.
-
Remove confusing part of sentence defining active EditContexts. w3c/edit-context#37, by @dandclark.
-
-
6 pull requests merged.
-
Fix event firing to match arguments expected by `fire an event` w3c/edit-context#47.
-
Update TextUpdateEventInit field names w3c/edit-context#46.
-
Update supported elements w3c/edit-context#44.
-
Remove mention of 'parallel' from 'Update the Text Edit Context' w3c/edit-context#45.
-
Expand events section and clarify that updateCharacterBounds can be async w3c/edit-context#43.
-
Remove confusing part of sentence defining active EditContexts. w3c/edit-context#37.
-
-
1 pull request closed.
-
Add event interfaces to 'fire an event' phrases w3c/edit-context#31.
-
-
2 pull requests received 6 new comments.
-
Add event interfaces to 'fire an event' phrases w3c/edit-context#31 (4 comments by @dandclark, @snianu)
-
w3c/editing
-
6 issues opened.
-
Define behavior of pressing enter in inline editing host w3c/editing#430, by @foolip.
-
TPAC 2023 participation w3c/editing#429, by @johanneswilm.
-
TPAC 2023 participation w3c/editing#428, by @johanneswilm.
-
TPAC 2023 participation - Call for topics w3c/editing#427, by @johanneswilm.
-
[EditContext] Issues for May 11 meeting w3c/editing#426, by @dandclark.
-
-
3 issues closed.
-
[EditContext] Issues for May 11 meeting w3c/editing#426.
-
TPAC 2023 participation w3c/editing#429.
-
TPAC 2023 participation w3c/editing#428.
-
-
4 issues received 11 new comments.
-
Define behavior of pressing enter in inline editing host w3c/editing#430 (4 comments by @foolip, @masayuki-nakano)
-
[Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? w3c/editing#424 (4 comments by @evanstade, @fergald, @snianu)
-
[Delayed Clipboard Rendering] Does macOS support setting the data for the requested pasteboard item asynchronously? w3c/editing#425 (2 comments by @snianu)
-
-
1 pull request opened.
-
Mark the copy of the EditContext explainer in this repo as archived w3c/editing#431, by @dandclark.
-
-
2 pull requests merged.
-
Mark the copy of the EditContext explainer in this repo as archived w3c/editing#431.
-
Update meeting invite link w3c/editing#391.
-
w3c/clipboard-apis
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Mark up definition of events following bikeshed conventions w3c/clipboard-apis#181.
-
-
1 pull request received 2 new comments.
Past meetings
GitHub
w3c/editing
-
2 issues opened.
-
Delayed clipboard rendering API shape. w3c/editing#423, by @snianu.
-
2 issues received 4 new comments.
-
Seeking feedback on delayed clipboard rendering proposal w3c/editing#417 (2 comments by @saschanaz, @smaug----)
-
[Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? w3c/editing#424 (2 comments by @inexorabletash, @snianu)
-
w3c/virtual-keyboard
-
1 issue opened.
-
Question: API isn't accessible in unsecure context? w3c/virtual-keyboard#20, by @woody-li.
-
-
1 issue received 2 new comments.
-
Question: API isn't accessible in unsecure context? w3c/virtual-keyboard#20 (2 comments by @HolgerJeromin, @woody-li)
-
w3c/selection-api
-
4 issues opened.
-
toString should return the selected text in input / textarea element w3c/selection-api#165, by @rniwa.
-
Should TreeWalker be expanded to support shadow roots in support of the selection API? w3c/selection-api#164, by @keithamus.
-
Serialization of the current selection, when that selection crosses shadow roots w3c/selection-api#163, by @keithamus.
-
collapse() and extend() should not exit early when called with a node within a shadow tree w3c/selection-api#162, by @rniwa.
-
-
3 issues closed.
-
toString should return the selected text in input / textarea element w3c/selection-api#165.
-
Should TreeWalker be expanded to support shadow roots in support of the selection API? w3c/selection-api#164.
-
collapse() and extend() should not exit early when called with a node within a shadow tree w3c/selection-api#162.
-
-
3 issues received 4 new comments.
-
Should TreeWalker be expanded to support shadow roots in support of the selection API? w3c/selection-api#164 (1 comment by @rniwa)
-
collapse() and extend() should not exit early when called with a node within a shadow tree w3c/selection-api#162 (1 comment by @rniwa)
w3c/clipboard-apis
-
1 issue received 1 new comment.
w3c/edit-context
-
1 pull request opened.
-
Update demos to handle textupdate event changes in https://chromium-r… w3c/edit-context#35, by @dandclark.
-
-
1 pull request merged.
-
Update demos to handle textupdate event changes in https://chromium-r… w3c/edit-context#35.
-
Past meetings
Participants
-
1 participant joined.
-
Bo Cupp (Microsoft Corporation) joined.
-
GitHub
w3c/selection-api
-
1 issue received 8 new comments.
w3c/editing
-
1 issue opened.
-
Behavior of insert* commands for contenteditable=plaintext-only w3c/editing#419, by @zcorpan.
-
-
2 issues received 28 new comments.
-
Seeking feedback on delayed clipboard rendering proposal w3c/editing#417 (24 comments by @annevk, @benjamind, @evanstade, @fergald, @inexorabletash, @megangardner, @mkruisselbrink, @rakina, @sanketj, @snianu, @tilgovi, @whsieh)
-
-
3 pull requests opened.
-
Additional documents for unsanitized HTML read/write w3c/editing#422, by @anaskim.
-
Mark the old EditContext spec as archived w3c/editing#421, by @dandclark.
-
Add unsanitized html read/write doc. w3c/editing#420, by @snianu.
-
-
4 pull requests merged.
-
Additional documents for unsanitized HTML read/write w3c/editing#422.
-
Mark the old EditContext spec as archived w3c/editing#421.
-
Add unsanitized html read/write doc. w3c/editing#420.
-
Define `contenteditable=plaintext-only` w3c/editing#407.
-
-
3 pull requests received 14 new comments.
-
Additional documents for unsanitized HTML read/write w3c/editing#422 (7 comments by @anaskim, @snianu)
-
w3c/clipboard-apis
-
1 pull request received 2 new comments.
w3c/edit-context
-
1 issue opened.
-
The `compositionend` event is no longer fired w3c/edit-context#34, by @tidoust.
-
-
5 issues closed.
-
Typo in "Extensions to the Element interface" w3c/edit-context#32.
-
"Squiggle" should be "Wavy" as a value of underlineStyle of TextFormat w3c/edit-context#29.
-
EditContext.isInComposition should be renamed to `isComposing` w3c/edit-context#24.
-
EditContext: should editContext be on Element? w3c/edit-context#18.
-
EditContext: event constructors are wrong w3c/edit-context#16.
-
-
1 pull request opened.
-
add more details to the spec and address issue #16 #18 #24 #29 #32 w3c/edit-context#33, by @alexkeng.
-
-
1 pull request merged.
-
add more details to the spec and address issue #16 #18 #24 #29 #32 w3c/edit-context#33.
-
Past meetings
Participants
-
1 participant joined.
-
Chris Harrelson (Google LLC) joined.
-
GitHub
w3c/input-events
-
1 pull request opened.
-
Adjust difference between level 1 and 2 w3c/input-events#142, by @johanneswilm.
-
w3c/editing
-
3 issues received 6 new comments.
-
Seeking feedback on delayed clipboard rendering proposal w3c/editing#417 (3 comments by @annevk, @johanneswilm)
-
w3c/selection-api
-
1 issue received 5 new comments.
w3c/clipboard-apis
-
1 issue received 1 new comment.
-
Replacing no-break spaces when converting HTML to plain text upon clipboard export w3c/clipboard-apis#173 (1 comment by @hsivonen)
-
Past meetings
Participants
-
1 participant left.
-
Bo Cupp (Microsoft Corporation) left.
-
GitHub
w3c/editing
-
2 issues closed.
-
Hi w3c/editing#418.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Change the types used on macOS w3c/editing#416.
-
-
1 pull request received 2 new comments.
w3c/input-events
-
1 issue received 1 new comment.
-
w3c/input-events#105 (1 comment by @kungfooman)
-
w3c/clipboard-apis
-
1 issue received 1 new comment.
-
What happens if promises to Blobs are not resolved within a reasonable amount of time? w3c/clipboard-apis#161 (1 comment by @saschanaz)
-
w3c/selection-api
-
1 issue received 1 new comment.