Web Editing Working Group - Activity in 2024
No matches.
TR publications
-
3 documents published.
-
EditContext API published twice as a Working Draft. History of EditContext API
-
Selection API published as a Working Draft. History of Selection API
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Howard Edwards (Bocoup) joined.
-
-
1 organization joined.
-
Bocoup joined.
-
GitHub
w3c/edit-context
-
1 issue received 3 new comments.
-
The interaction between composition and `updateText`/`updateSelection` should be more clearly defined w3c/edit-context#111 (3 comments by @dandclark, @johanneswilm, @marijnh)
-
-
2 pull requests opened.
-
Fix warnings from tidy-html w3c/edit-context#113, by @dandclark.
-
Fix image references and update control & selection bounds methods w3c/edit-context#112, by @ashishkum-ms.
-
-
2 pull requests merged.
-
Fix warnings from tidy-html w3c/edit-context#113.
-
Fix image references and update control & selection bounds methods w3c/edit-context#112.
-
w3c/selection-api
-
1 issue received 1 new comment.
-
w3c/selection-api#2 (1 comment by @dizhang168)
-
-
1 pull request opened.
-
chore: fix typo of `selectionchange` w3c/selection-api#343, by @wyattzheng.
-
-
1 pull request merged.
-
chore: fix typo of `selectionchange` w3c/selection-api#343.
-
-
2 pull requests received 3 new comments.
-
w3c/selection-api#340 (1 comment by @w3cbot)
w3c/input-events
-
2 issues opened.
-
Discuss or address possible implementor privacy and security relevant concerns w3c/input-events#171, by @pes10k.
-
Typo, nit, and clarity suggestions w3c/input-events#170, by @pes10k.
-
-
4 issues received 12 new comments.
-
Discuss or address possible implementor privacy and security relevant concerns w3c/input-events#171 (9 comments by @dandclark, @johanneswilm, @pes10k, @whsieh)
-
Keep native browser behavior for prevented `beforeinput` events w3c/input-events#161 (1 comment by @smaug----)
-
Should <input type=text> get beforeinput event when pressing enter and if yes, should it be cancelable so that submit can be prevented? w3c/input-events#160 (1 comment by @smaug----)
-
The default action of `beforeinput` does not define `<input>` and `<textarea>` cases w3c/input-events#156 (1 comment by @smaug----)
-
w3c/clipboard-apis
-
2 issues received 2 new comments.
-
Remove clipboardchange event (and replace it possibly with a promise returning method) w3c/clipboard-apis#228 (1 comment by @jyasskin)
-
w3c/clipboard-apis#70 (1 comment by @Kaiido)
-
-
1 pull request opened.
-
Fix ClipboardEvent example to include `eventInitDict` param w3c/clipboard-apis#231, by @F3n67u.
-
-
1 pull request received 1 new comment.
-
Fix ClipboardEvent example to include `eventInitDict` param w3c/clipboard-apis#231 (1 comment by @w3cbot)
-
w3c/editing
-
1 issue opened.
-
No-op in "delete the selection" algorithm with end block's parent w3c/editing#473, by @gmta.
-
-
1 issue received 2 new comments.
TR publications
-
2 documents published.
-
Selection API published as a Working Draft. History of Selection API
-
EditContext API published as a Working Draft. History of EditContext API
-
Past meetings
-
1 meeting.
Participants
-
1 Team contact appointed.
-
Michael[tm] Smith (sideshowbarker) became a Team contact.
-
-
1 Team contact stepped down.
-
Michael[tm] Smith (sideshowbarker) stepped down as a Team contact.
-
-
2 participants joined.
-
Andreas Kling (W3C Invited Experts) joined.
-
Michael[tm] Smith (sideshowbarker) (W3C) joined.
-
-
5 participants left.
-
Kashish Jain (Microsoft Corporation) left.
-
Saiqi Jia (Brickdoc) left.
-
huanyu cai (Brickdoc) left.
-
Yuhang Shi (Brickdoc) left.
-
Li Ding (Brickdoc) left.
-
-
1 organization left.
-
Brickdoc left.
-
GitHub
w3c/input-events
-
4 issues opened.
-
Consistency between `historyRedo` and `historyUndo`? w3c/input-events#169, by @aphillips.
-
typos on `insertTranspose` w3c/input-events#168, by @aphillips.
-
"temporal" confusing in `kill buffer` w3c/input-events#167, by @aphillips.
-
Horizontal Review of Input events w3c/input-events#166, by @siusin.
-
-
4 issues closed.
-
Code points and graphemes in backward deletion w3c/input-events#71.
-
TAG Review for InputEvent w3c/input-events#55.
-
Add accessibility section w3c/input-events#110.
-
-
7 issues received 10 new comments.
-
w3c/input-events#74 (1 comment by @siusin)
-
w3c/input-events#55 (1 comment by @siusin)
-
The default action of `beforeinput` does not define `<input>` and `<textarea>` cases w3c/input-events#156 (1 comment by @vlakoff)
-
w3c/input-events#110 (1 comment by @johanneswilm)
w3c/editing
-
1 issue opened.
-
Add mechanism to control enablement of handwriting w3c/editing#472, by @gastonrod.
-
-
3 issues received 3 new comments.
-
w3c/editing#158 (1 comment by @frederikheld)
-
Contenteditable re-creating deleted children when it shouldn't w3c/editing#468 (1 comment by @johanneswilm)
w3c/clipboard-apis
-
1 issue opened.
-
Add privacy considerations for the clipboardchange event w3c/clipboard-apis#230, by @jyasskin.
-
w3c/selection-api
-
1 issue closed.
-
Throw InvalidNodeTypeError on DocumentType nodes w3c/selection-api#118.
-
-
3 issues received 13 new comments.
-
Specify the behavior when DOM mutation occurs across shadow-crossing selection w3c/selection-api#168 (2 comments by @dizhang168)
-
w3c/selection-api#7 (1 comment by @Yaffle)
-
1 pull request opened.
-
Throw InvalidNodeTypeError for doctype more eagerly w3c/selection-api#342, by @awesomekling.
-
-
1 pull request merged.
-
Throw InvalidNodeTypeError for doctype more eagerly w3c/selection-api#342.
-
-
1 pull request closed.
-
Throw correct exceptions from collapse/selectAllChildren on detached doctypes w3c/selection-api#86.
-
-
2 pull requests received 5 new comments.
-
Throw InvalidNodeTypeError for doctype more eagerly w3c/selection-api#342 (4 comments by @rniwa, @sideshowbarker)
-
w3c/selection-api#86 (1 comment by @rniwa)
-
w3c/edit-context
-
1 issue opened.
-
1 pull request merged.
-
chore: markup cleanup w3c/edit-context#108.
-
-
1 pull request received 3 new comments.
TR publications
-
2 documents published.
-
Selection API published as a Working Draft. History of Selection API
-
Input Events Level 2 published as a Working Draft. History of Input Events Level 2
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Rohan Raja (Microsoft Corporation) joined.
-
-
1 participant left.
-
Howard Edwards (Bocoup) left.
-
-
1 organization left.
-
Bocoup left.
-
GitHub
w3c/selection-api
-
2 issues opened.
-
Scheduling an selectionchange event does not set "has scheduled selectionchange event" to true w3c/selection-api#338, by @gmta.
-
Improve selection.isCollapsed w3c/selection-api#337, by @abhish-shrivastava.
-
-
1 issue closed.
-
Add `selectionRoot` option to getComposedRanges parameter options w3c/selection-api#180.
-
-
8 issues received 21 new comments.
-
Define to remove selection range automatically if a selection range is modified into different selection root w3c/selection-api#175 (1 comment by @dizhang168)
-
Specify the behavior when DOM mutation occurs across shadow-crossing selection w3c/selection-api#168 (1 comment by @dizhang168)
-
Add `selectionRoot` option to getComposedRanges parameter options w3c/selection-api#180 (1 comment by @dizhang168)
-
w3c/selection-api#3 (1 comment by @Gingeh)
-
Need spec changes to Range and StaticRange to support nodes in different tree? w3c/selection-api#169 (1 comment by @johanneswilm)
-
2 pull requests opened.
-
Reference the move primitive in DOM mutations section w3c/selection-api#341, by @domfarolino.
-
Editorial: Correctly reference `{{Document/getSelection()}}` w3c/selection-api#339, by @domfarolino.
-
-
1 pull request merged.
-
Editorial: Correctly reference `{{Document/getSelection()}}` w3c/selection-api#339.
-
-
1 pull request received 1 new comment.
-
Editorial: Correctly reference `{{Document/getSelection()}}` w3c/selection-api#339 (1 comment by @rniwa)
-
w3c/virtual-keyboard
-
1 issue received 1 new comment.
-
Get VK’s `boundingRect` before it is shown (`beforegeometrychange` event) w3c/virtual-keyboard#24 (1 comment by @josephrocca)
-
w3c/clipboard-apis
-
1 issue opened.
-
SVG sanitization not defined w3c/clipboard-apis#229, by @annevk.
-
-
2 issues received 2 new comments.
-
ClipboardChange event spec: Callout transient user activation should be applied for focus requirement. w3c/clipboard-apis#225 (1 comment by @johanneswilm)
-
w3c/input-events
-
3 issues closed.
-
'deleteWordForwards' and 'deleteWordBackwards' not well defined w3c/input-events#72.
-
July 29th F2F Agenda Item - Non-cancelable event 2 of 2 w3c/input-events#17.
-
Add Internationalization Considerations section w3c/input-events#109.
-
-
8 issues received 13 new comments.
-
Clarify what `getTargetRanges` should return when joining paragraphs w3c/input-events#159 (2 comments by @johanneswilm, @masayuki-nakano)
-
Clarify what `getTargetRanges` should return when all content in an inline element is removed w3c/input-events#158 (2 comments by @johanneswilm, @masayuki-nakano)
-
w3c/input-events#17 (1 comment by @johanneswilm)
-
The default action of `beforeinput` does not define `<input>` and `<textarea>` cases w3c/input-events#156 (1 comment by @johanneswilm)
-
Keep native browser behavior for prevented `beforeinput` events w3c/input-events#161 (1 comment by @johanneswilm)
-
Clarify whether `dataTransfer` may have `text/html` when pasting rich text into `contenteditable=plaintext-only` w3c/input-events#162 (1 comment by @johanneswilm)
-
1 pull request opened.
-
"text" => "content" w3c/input-events#164, by @johanneswilm.
-
-
1 pull request merged.
-
"text" => "content" w3c/input-events#164.
-
-
1 pull request received 1 new comment.
-
w3c/input-events#165 (1 comment by @w3cbot)
-
w3c/edit-context
-
1 issue opened.
-
Publish FPWD w3c/edit-context#109, by @johanneswilm.
-
-
1 issue closed.
-
Publish FPWD w3c/edit-context#109.
-
-
3 issues received 3 new comments.
-
How does characterboundsupdate interact with multi-codeunit characters? w3c/edit-context#96 (1 comment by @johanneswilm)
-
1 pull request opened.
-
chore: update the group decision for auto-pub w3c/edit-context#110, by @siusin.
-
-
1 pull request merged.
-
chore: update the group decision for auto-pub w3c/edit-context#110.
-
w3c/editing
-
1 issue opened.
-
CfC: Enable automated publication system for all Web Editing WG specs w3c/editing#471, by @johanneswilm.
-
-
1 issue closed.
-
3 issues received 5 new comments.
-
Contenteditable re-creating deleted children when it shouldn't w3c/editing#468 (3 comments by @johanneswilm, @masayuki-nakano)
-
CfC: Enable automated publication system for all Web Editing WG specs w3c/editing#471 (1 comment by @siusin)
-
Clarify the nested case of `contenteditable=true` and `contenteditable=plaintext-only` w3c/editing#470 (1 comment by @johanneswilm)
-
TR publications
-
4 documents published.
-
Selection API published 3 times as a Working Draft. History of Selection API
-
Input Events Level 2 published as a Working Draft. History of Input Events Level 2
-
Past meetings
Participants
-
1 participant joined.
-
Mason Freed (Google LLC) joined.
-
GitHub
w3c/selection-api
-
1 issue opened.
-
Flat Tree or Composed Tree w3c/selection-api#336, by @dizhang168.
-
-
1 issue closed.
-
Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary w3c/selection-api#176.
-
-
5 issues received 9 new comments.
-
Need spec changes to Range and StaticRange to support nodes in different tree? w3c/selection-api#169 (3 comments by @dizhang168)
-
Add `selectionRoot` option to getComposedRanges parameter options w3c/selection-api#180 (2 comments by @dizhang168, @mfreed7)
-
w3c/selection-api#7 (1 comment by @fabiospampinato)
-
Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary w3c/selection-api#176 (1 comment by @rniwa)
-
-
1 pull request merged.
-
Change getComposedRanges to have options as input w3c/selection-api#331.
-
-
1 pull request received 5 new comments.
-
Change getComposedRanges to have options as input w3c/selection-api#331 (5 comments by @annevk, @dizhang168)
-
w3c/edit-context
-
1 issue opened.
-
EditContext.text can be problematic from performance point of view w3c/edit-context#107, by @smaug----.
-
-
1 issue closed.
-
Chrome error and list of IMEs and what we should expect? w3c/edit-context#105.
-
-
2 issues received 10 new comments.
-
Extending the list of supported elements w3c/edit-context#103 (5 comments by @dandclark, @smaug----)
-
How does characterboundsupdate interact with multi-codeunit characters? w3c/edit-context#96 (5 comments by @dandclark, @marijnh, @TheSpyder)
-
-
2 pull requests opened.
-
chore: markup cleanup w3c/edit-context#108, by @siusin.
-
set up auto-publication w3c/edit-context#106, by @siusin.
-
-
1 pull request merged.
-
set up auto-publication w3c/edit-context#106.
-
w3c/clipboard-apis
-
7 issues opened.
-
Remove clipboardchange event (and replace it possibly with a promise returning method) w3c/clipboard-apis#228, by @smaug----.
-
Clipboard Change Event API w3c/clipboard-apis#227, by @ragoulik.
-
ClipboardChange even spec: Callout details for cross-origin iframes and fencedframes w3c/clipboard-apis#226, by @ragoulik.
-
ClipboardChange event spec: Callout transient user activation should be applied for focus requirement. w3c/clipboard-apis#225, by @ragoulik.
-
ClipboardChange event spec: Callout clipboard-read permission is required to listen to clipboardchange w3c/clipboard-apis#224, by @ragoulik.
-
beforecopy, beforecut, and beforepaste events w3c/clipboard-apis#222, by @annevk.
-
-
2 issues received 2 new comments.
-
ClipboardChange event spec: Callout clipboard-read permission is required to listen to clipboardchange w3c/clipboard-apis#224 (1 comment by @saschanaz)
w3c/input-events
-
5 issues opened.
-
Keep native browser behavior for prevented `beforeinput` events w3c/input-events#161, by @Comandeer.
-
Clarify what `getTargetRanges` should return when joining paragraphs w3c/input-events#159, by @masayuki-nakano.
-
1 issue closed.
-
5 issues received 27 new comments.
-
Clarify what `getTargetRanges` should return when all content in an inline element is removed w3c/input-events#158 (12 comments by @johanneswilm, @masayuki-nakano, @smaug----)
-
Clarify what `getTargetRanges` should return when joining paragraphs w3c/input-events#159 (6 comments by @johanneswilm, @masayuki-nakano, @smaug----)
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (6 comments by @johanneswilm, @masayuki-nakano, @smaug----)
-
Clarify whether `dataTransfer` may have `text/html` when pasting rich text into `contenteditable=plaintext-only` w3c/input-events#162 (2 comments by @masayuki-nakano, @smaug----)
-
The default action of `beforeinput` does not define `<input>` and `<textarea>` cases w3c/input-events#156 (1 comment by @smaug----)
-
-
1 pull request merged.
-
Add PR template w3c/input-events#157.
-
w3c/editing
-
4 issues opened.
-
TPAC 2024 agenda (preliminary) 2024-09-26 w3c/editing#469, by @johanneswilm.
-
Contenteditable re-creating deleted children when it shouldn't w3c/editing#468, by @johanneswilm.
-
Broken links in execCommand w3c/editing#466, by @dontcallmedom-bot.
-
2 issues closed.
-
Explore if there are better meeting times for the Web Editing WG w3c/editing#359.
-
TPAC 2022 w3c/editing#400.
-
-
4 issues received 5 new comments.
-
Contenteditable re-creating deleted children when it shouldn't w3c/editing#468 (2 comments by @johanneswilm, @saschanaz)
-
Clarify the nested case of `contenteditable=true` and `contenteditable=plaintext-only` w3c/editing#470 (1 comment by @rniwa)
-
RFC: Contenteditable "indent"/"outdent" implementations are not aligned with popular editors w3c/editing#437 (1 comment by @johanneswilm)
-
RFC: What is expected when a root editable element's contents are completely removed via execCommand w3c/editing#455 (1 comment by @masayuki-nakano)
-
-
1 pull request opened.
-
Update execCommand editor to Simon Pieters w3c/editing#467, by @johanneswilm.
-
-
1 pull request merged.
-
Update execCommand editor to Simon Pieters w3c/editing#467.
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Abhishek Singh (Microsoft Corporation) joined.
-
Di Zhang (Google LLC) joined.
-
Rakesh Goulikar (Microsoft Corporation) joined.
-
GitHub
w3c/edit-context
-
1 issue opened.
-
Chrome error and list of IMEs and what we should expect? w3c/edit-context#105, by @talltyler.
-
-
4 issues received 7 new comments.
-
What are the most significant benefits of the EditContext API compared to hidden textarea ? w3c/edit-context#102 (3 comments by @devlzl, @talltyler)
-
Extending the list of supported elements w3c/edit-context#103 (2 comments by @Comandeer, @dandclark)
-
Chrome error and list of IMEs and what we should expect? w3c/edit-context#105 (1 comment by @dandclark)
-
-
1 pull request merged.
-
Add PR template w3c/edit-context#100.
-
-
1 pull request received 1 new comment.
w3c/selection-api
-
2 issues opened.
-
`Selection.direction`'s behavior should be based on the node's position w3c/selection-api#334, by @mozesstumpf.
-
`selectionchange` fires differently across the browser engines w3c/selection-api#332, by @mozesstumpf.
-
-
2 issues closed.
-
`Selection.direction`'s behavior should be based on the node's position w3c/selection-api#334.
-
`selectionchange` fires differently across the browser engines w3c/selection-api#332.
-
-
4 issues received 19 new comments.
-
`Selection.direction`'s behavior should be based on the node's position w3c/selection-api#334 (11 comments by @mozesstumpf, @rniwa)
-
Need spec changes to Range and StaticRange to support nodes in different tree? w3c/selection-api#169 (4 comments by @annevk, @mfreed7)
-
Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary w3c/selection-api#176 (2 comments by @sanketj, @whsieh)
-
`selectionchange` fires differently across the browser engines w3c/selection-api#332 (2 comments by @mozesstumpf, @rniwa)
-
-
2 pull requests opened.
-
Update PR template w3c/selection-api#333, by @sanketj.
-
Change getComposedRanges to have options as input w3c/selection-api#331, by @dizhang168.
-
-
1 pull request merged.
-
Update PR template w3c/selection-api#333.
-
-
1 pull request received 2 new comments.
w3c/clipboard-apis
-
3 pull requests opened.
-
Add link to explainer doc for clipboardchange event w3c/clipboard-apis#221, by @roraja.
-
Update PR template w3c/clipboard-apis#220, by @sanketj.
-
Remove issues claiming "clipboard-write" was removed w3c/clipboard-apis#219, by @foolip.
-
-
1 pull request merged.
-
Update PR template w3c/clipboard-apis#220.
-
-
1 pull request received 4 new comments.
-
Remove issues claiming "clipboard-write" was removed w3c/clipboard-apis#219 (4 comments by @annevk, @foolip, @saschanaz)
-
w3c/input-events
-
1 issue received 4 new comments.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (4 comments by @dandclark, @johanneswilm, @smaug----)
-
-
1 pull request opened.
-
Add PR template w3c/input-events#157, by @sanketj.
-
w3c/editing
-
1 issue opened.
-
1 issue closed.
-
1 pull request opened.
-
1 pull request merged.
-
1 pull request received 1 new comment.
-
[execCommand] Fixed newline Unicode character for insertText action command step 5. w3c/editing#465 (1 comment by @w3cbot)
-
GitHub
w3c/selection-api
-
2 issues opened.
-
Add `selectionRoot` option to getComposedRanges parameter options w3c/selection-api#180, by @dizhang168.
-
-
1 issue closed.
-
1 issue reopened.
-
Selection.direction spec issue, what should happen on multiple click? w3c/selection-api#177, by @annevk.
-
-
6 issues received 10 new comments.
-
Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary w3c/selection-api#176 (2 comments by @dizhang168, @sefeng211)
-
Add `selectionRoot` option to getComposedRanges parameter options w3c/selection-api#180 (2 comments by @dizhang168, @mfreed7)
-
Need spec changes to Range and StaticRange to support nodes in different tree? w3c/selection-api#169 (2 comments by @dizhang168, @mfreed7)
-
Selection.direction spec issue, what should happen on multiple click? w3c/selection-api#177 (2 comments by @annevk, @sefeng211)
-
Clarify how `selection.modify()` when the granularity parameter is `paragraphboundary` handles non-editable elements in an editing host w3c/selection-api#179 (1 comment by @zp1996)
-
Clarify how `selection.modify()` when the granularity parameter is `paragraph` handles non-editable elements in an editing host w3c/selection-api#173 (1 comment by @zp1996)
-
w3c/input-events
-
1 issue opened.
-
The default action of `beforeinput` does not define `<input>` and `<textarea>` cases w3c/input-events#156, by @masayuki-nakano.
-
-
1 issue received 2 new comments.
-
The default action of `beforeinput` does not define `<input>` and `<textarea>` cases w3c/input-events#156 (2 comments by @johanneswilm, @vlakoff)
-
w3c/edit-context
-
3 issues opened.
-
`EditContext.text` should not extend by default w3c/edit-context#104, by @mozesstumpf.
-
Extending the list of supported elements w3c/edit-context#103, by @Comandeer.
-
What are the most significant benefits of the EditContext API compared to hidden textarea ? w3c/edit-context#102, by @devlzl.
-
-
1 issue received 2 new comments.
-
What are the most significant benefits of the EditContext API compared to hidden textarea ? w3c/edit-context#102 (2 comments by @DavidMulder0, @devlzl)
-
TR publications
-
2 documents published.
-
Input Events Level 2 published twice as a Working Draft. History of Input Events Level 2
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Siye Liu (Microsoft Corporation) joined.
-
Samba Murthy Bandaru (Microsoft Corporation) joined.
-
GitHub
w3c/selection-api
-
1 issue opened.
-
Update the "published by" metadata w3c/selection-api#178, by @jyasskin.
-
-
2 issues received 2 new comments.
-
Clarify how `selection.modify()` when the granularity parameter is `paragraph` handles non-editable elements in an editing host w3c/selection-api#173 (1 comment by @zp1996)
-
Selection.direction spec issue, what should happen on multiple click? w3c/selection-api#177 (1 comment by @zcorpan)
-
w3c/edit-context
-
1 issue opened.
-
EditContext spec doesn't specify event types / names w3c/edit-context#99, by @rniwa.
-
-
1 issue closed.
-
Need to specify which input types are handled by EditContext w3c/edit-context#94.
-
-
1 issue received 3 new comments.
-
Handling 'backwards' selection direction in an EditContext implementation w3c/edit-context#81 (3 comments by @dandclark, @marijnh)
-
-
2 pull requests opened.
-
Specify inputTypes handled by EditContext w3c/edit-context#101, by @dandclark.
-
Add PR template w3c/edit-context#100, by @sanketj.
-
-
1 pull request merged.
-
Specify inputTypes handled by EditContext w3c/edit-context#101.
-
-
2 pull requests received 35 new comments.
-
Add PR template w3c/edit-context#100 (34 comments by @dandclark, @johanneswilm, @sanketj, @saschanaz)
-
w3c/input-events
-
2 issues received 2 new comments.
-
event order proposal when inserting replacement text such as text prediction, spell checker, etc. w3c/input-events#152 (1 comment by @garykac)
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (1 comment by @css-meeting-bot)
-
-
2 pull requests opened.
-
Link to EditContext-handled inputTypes w3c/input-events#154, by @dandclark.
-
Fix typos in index.html w3c/input-events#153, by @zzzzBov.
-
-
2 pull requests merged.
-
Link to EditContext-handled inputTypes w3c/input-events#154.
-
Fix typos in index.html w3c/input-events#153.
-
-
1 pull request received 1 new comment.
w3c/clipboard-apis
-
2 issues opened.
-
Support clipboard write() for audio formats (midi, wav) w3c/clipboard-apis#218, by @chr15m.
-
Write UTF-8 data to the clipboard. w3c/clipboard-apis#217, by @snianu.
-
-
1 issue closed.
-
Make it possible to read image/svg+xml from the clipboard w3c/clipboard-apis#92.
-
-
1 issue reopened.
-
Support clipboard write() for audio formats (midi, wav) w3c/clipboard-apis#218, by @tomayac.
-
-
2 issues received 11 new comments.
-
Support clipboard write() for audio formats (midi, wav) w3c/clipboard-apis#218 (8 comments by @chr15m, @saschanaz, @tomayac)
-
Write UTF-8 data to the clipboard. w3c/clipboard-apis#217 (3 comments by @annevk, @css-meeting-bot, @snianu)
-
-
1 pull request opened.
-
Add SVG format to the spec. w3c/clipboard-apis#216, by @snianu.
-
-
1 pull request merged.
-
Add SVG format to the spec. w3c/clipboard-apis#216.
-
-
1 pull request received 2 new comments.
w3c/editing
-
1 issue closed.
-
TPAC 2024 participation w3c/editing#462.
-
-
1 issue received 1 new comment.
-
normative spec changes do not always end up as issues filed with browsers w3c/editing#463 (1 comment by @css-meeting-bot)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Kashish Jain (Microsoft Corporation) joined.
-
GitHub
w3c/clipboard-apis
-
2 issues received 4 new comments.
-
2 pull requests opened.
-
Split implementor interest and implementation bugs from PR template w3c/clipboard-apis#215, by @saschanaz.
-
The permission request stuff is no longer in contention w3c/clipboard-apis#214, by @martinthomson.
-
-
2 pull requests received 16 new comments.
-
Split implementor interest and implementation bugs from PR template w3c/clipboard-apis#215 (15 comments by @annevk, @johanneswilm, @sanketj, @saschanaz, @snianu)
-
The permission request stuff is no longer in contention w3c/clipboard-apis#214 (1 comment by @annevk)
-
w3c/selection-api
-
2 issues opened.
-
Selection.direction spec issue, what should happen on multiple click? w3c/selection-api#177, by @mozesstumpf.
-
Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary w3c/selection-api#176, by @siliu1.
-
-
2 issues received 7 new comments.
-
Change `getComposedRanges`'s `shadowRoots` parameter from rest parameter to a dictionary w3c/selection-api#176 (5 comments by @mfreed7, @sefeng211, @siliu1, @smaug----)
-
Selection.direction spec issue, what should happen on multiple click? w3c/selection-api#177 (2 comments by @annevk, @mozesstumpf)
-
-
1 pull request received 2 new comments.
-
Fixes https://github.com/w3c/selection-api/issues/170. w3c/selection-api#172 (2 comments by @rniwa, @smaug----)
-
w3c/editing
-
1 issue opened.
-
TPAC 2024 participation w3c/editing#462, by @johanneswilm.
-
-
1 issue closed.
-
Upstream changes from trusted types w3c/editing#461.
-
-
1 issue reopened.
-
Removal of browser built-in Undo stack functionality from contenteditable w3c/editing#150, by @johanneswilm.
-
-
3 issues received 5 new comments.
-
normative spec changes do not always end up as issues filed with browsers w3c/editing#463 (2 comments by @css-meeting-bot, @sanketj)
-
-
1 pull request merged.
-
Upstream changes from Trusted Types w3c/editing#460.
-
w3c/edit-context
-
1 issue received 3 new comments.
-
Need to specify which input types are handled by EditContext w3c/edit-context#94 (3 comments by @css-meeting-bot, @dandclark)
-
w3c/input-events
-
1 issue opened.
-
event order proposal when inserting replacement text such as text prediction, spell checker, etc. w3c/input-events#152, by @siliu1.
-
-
2 issues received 7 new comments.
-
event order proposal when inserting replacement text such as text prediction, spell checker, etc. w3c/input-events#152 (4 comments by @css-meeting-bot, @johanneswilm, @siliu1)
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (3 comments by @css-meeting-bot, @dandclark, @masayuki-nakano)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Taylore Givens (Microsoft Corporation) joined.
-
GitHub
w3c/clipboard-apis
-
1 issue opened.
-
No provision made for multiple clipboards, e.g. on Linux w3c/clipboard-apis#213, by @keysmashes.
-
-
2 issues received 4 new comments.
-
Feature detection for supported clipboard formats w3c/clipboard-apis#170 (2 comments by @saschanaz, @yisibl)
-
Option to specify ClipboardItem is sensitive in .write() and .writeText() w3c/clipboard-apis#154 (2 comments by @oliverdunk, @snianu)
-
w3c/edit-context
-
4 issues opened.
-
Undo manager w3c/edit-context#98, by @mitar.
-
Representing state changes as multiple distinct asynchronous events can be awkward w3c/edit-context#97, by @marijnh.
-
How does characterboundsupdate interact with multi-codeunit characters? w3c/edit-context#96, by @marijnh.
-
Making it possible to associate the EditContext with multiple Elements w3c/edit-context#95, by @mozesstumpf.
-
-
1 issue received 1 new comment.
w3c/editing
-
2 issues opened.
-
normative spec changes do not always end up as issues filed with browsers w3c/editing#463, by @johanneswilm.
-
Upstream changes from trusted types w3c/editing#461, by @lukewarlow.
-
-
3 issues received 8 new comments.
-
normative spec changes do not always end up as issues filed with browsers w3c/editing#463 (5 comments by @johanneswilm, @marcoscaceres)
-
w3c/input-events
-
1 issue received 1 new comment.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (1 comment by @css-meeting-bot)
-
-
1 pull request received 2 new comments.
-
Update intention for insertReplacementText to include writing suggestions w3c/input-events#149 (2 comments by @johanneswilm, @marcoscaceres)
-
w3c/selection-api
-
1 issue opened.
-
3 issues received 3 new comments.
-
Define `Selection.rangeCount` when an input field is focused w3c/selection-api#166 (1 comment by @masayuki-nakano)
-
Specify the behavior when DOM mutation occurs across shadow-crossing selection w3c/selection-api#168 (1 comment by @masayuki-nakano)
-
Clarify how `selection.modify()` when the granularity parameter is `paragraph` handles non-editable elements in an editing host w3c/selection-api#173 (1 comment by @zp1996)
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Luke Warlow (Igalia) joined.
-
Christine Hollingsworth (Google LLC) joined.
-
-
1 organization joined.
-
Igalia joined.
-
GitHub
w3c/editing
-
1 issue closed.
-
Status of specs we are working on w3c/editing#413.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Upstream changes from Trusted Types w3c/editing#460, by @lukewarlow.
-
-
1 pull request received 1 new comment.
w3c/selection-api
-
3 issues opened.
-
Migrate away from "queue a task" w3c/selection-api#174, by @annevk.
-
Selection.direction doesn't handle multiple ranges w3c/selection-api#171, by @smaug----.
-
-
1 issue closed.
-
Skip posting a task for `selectionchange` event in some cases w3c/selection-api#170.
-
-
3 issues received 8 new comments.
-
Skip posting a task for `selectionchange` event in some cases w3c/selection-api#170 (4 comments by @rniwa, @ShuangshuangZhou)
-
Need spec changes to Range and StaticRange to support nodes in different tree? w3c/selection-api#169 (2 comments by @emilio, @sefeng211)
-
Selection.direction doesn't handle multiple ranges w3c/selection-api#171 (2 comments by @rniwa, @smaug----)
-
-
1 pull request opened.
-
Fixes https://github.com/w3c/selection-api/issues/170. w3c/selection-api#172, by @rniwa.
-
-
1 pull request merged.
-
Fixes https://github.com/w3c/selection-api/issues/170. w3c/selection-api#172.
-
-
1 pull request received 7 new comments.
-
Fixes https://github.com/w3c/selection-api/issues/170. w3c/selection-api#172 (7 comments by @annevk, @rniwa, @ShuangshuangZhou)
-
w3c/input-events
-
1 issue received 1 new comment.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (1 comment by @css-meeting-bot)
-
-
1 pull request received 3 new comments.
-
Update intention for insertReplacementText to include writing suggestions w3c/input-events#149 (3 comments by @johanneswilm, @marcoscaceres)
-
w3c/clipboard-apis
-
3 issues received 3 new comments.
-
w3c/clipboard-apis#101 (1 comment by @wandyezj)
-
w3c/clipboard-apis#137 (1 comment by @css-meeting-bot)
-
Read Blob data for the supported formats on-demand during getType. w3c/clipboard-apis#191 (1 comment by @css-meeting-bot)
-
-
1 pull request received 1 new comment.
-
w3c/clipboard-apis#120 (1 comment by @wandyezj)
-
w3c/edit-context
-
2 issues opened.
-
Need to specify which input types are handled by EditContext w3c/edit-context#94, by @dandclark.
-
Backspace doesn't delete text in canvas w3c/edit-context#93, by @ilantc.
-
-
1 issue closed.
-
Backspace doesn't delete text in canvas w3c/edit-context#93.
-
-
3 issues received 4 new comments.
-
Need to specify which input types are handled by EditContext w3c/edit-context#94 (1 comment by @johanneswilm)
-
Should selection start/end be limited to the size of the text? w3c/edit-context#88 (1 comment by @dandclark)
w3c/virtual-keyboard
-
1 issue opened.
-
Get VK’s `boundingRect` before it is shown (`beforegeometrychange` event) w3c/virtual-keyboard#24, by @bramus.
-
Past meetings
-
1 meeting.
GitHub
w3c/clipboard-apis
-
1 issue opened.
-
[Async Clipboard API] Use Stream APIs to provide data during write w3c/clipboard-apis#212, by @snianu.
-
-
2 issues closed.
-
Topic: ‘unsanitized’ option to allow developers to opt-out of UA-provided sanitization w3c/clipboard-apis#206.
-
`supports` should take a dictionary instead of a DOMString as argument for readability w3c/clipboard-apis#211.
-
-
6 issues received 19 new comments.
-
[Async Clipboard API] Use Stream APIs to provide data during write w3c/clipboard-apis#212 (10 comments by @saschanaz, @snianu)
-
Should clipboard-write permission be removed too? w3c/clipboard-apis#163 (2 comments by @evanstade, @robertknight)
-
w3c/clipboard-apis#105 (1 comment by @yisibl)
-
Read Blob data for the supported formats on-demand during getType. w3c/clipboard-apis#191 (1 comment by @snianu)
-
`supports` should take a dictionary instead of a DOMString as argument for readability w3c/clipboard-apis#211 (1 comment by @snianu)
-
-
1 pull request merged.
-
Add non-normative and optional texts. w3c/clipboard-apis#208.
-
-
1 pull request received 4 new comments.
w3c/selection-api
-
1 issue opened.
-
Skip posting a task for `selectionchange` event in some cases w3c/selection-api#170, by @ShuangshuangZhou.
-
-
1 issue received 11 new comments.
-
Skip posting a task for `selectionchange` event in some cases w3c/selection-api#170 (11 comments by @annevk, @rniwa, @ShuangshuangZhou, @tkent-google)
-
w3c/editing
-
1 issue opened.
-
Delayed clipboard rendering TAG feedback w3c/editing#459, by @martinthomson.
-
-
4 issues received 18 new comments.
-
Support navigator.clipboard inside of Service Workers w3c/editing#458 (9 comments by @css-meeting-bot, @patrickkettner, @smaug----, @snianu)
-
[Delayed Clipboard Rendering] Privacy issue while reading data for web custom types w3c/editing#439 (4 comments by @annevk, @css-meeting-bot, @hober, @snianu)
-
Define behavior of pressing enter in inline editing host w3c/editing#430 (2 comments by @foolip, @zcorpan)
-
w3c/edit-context
-
1 issue opened.
-
Undo Functionality Not Working? w3c/edit-context#92, by @testsys-murali.
-
-
2 issues closed.
-
Spec defines 'double' in a way that collides with WebIDL w3c/edit-context#89.
-
Handling 'backwards' selection direction in an EditContext implementation w3c/edit-context#81.
-
-
1 issue reopened.
-
Handling 'backwards' selection direction in an EditContext implementation w3c/edit-context#81, by @dandclark.
-
-
2 issues received 5 new comments.
-
Handling 'backwards' selection direction in an EditContext implementation w3c/edit-context#81 (4 comments by @captainbrosset, @dandclark)
-
Spec defines 'double' in a way that collides with WebIDL w3c/edit-context#89 (1 comment by @css-meeting-bot)
-
-
2 pull requests opened.
-
Remove 'double' UnderlineStyle w3c/edit-context#91, by @dandclark.
-
Add note that updateText can have rangeStart > rangeEnd w3c/edit-context#90, by @dandclark.
-
-
2 pull requests merged.
-
Remove 'double' UnderlineStyle w3c/edit-context#91.
-
Add note that updateText can have rangeStart > rangeEnd w3c/edit-context#90.
-
w3c/input-events
-
1 issue received 1 new comment.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (1 comment by @css-meeting-bot)
-
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.
-
Etienne Noël (Google LLC) joined.
-
GitHub
w3c/clipboard-apis
-
3 issues opened.
-
`supports` should take a dictionary instead of a DOMString as argument for readability w3c/clipboard-apis#211, by @snianu.
-
RTF is not exposed when using navigator.clipboard.read() w3c/clipboard-apis#210, by @vmiklos.
-
read(formats) ambiguous w3c/clipboard-apis#209, by @evanstade.
-
-
3 issues received 10 new comments.
-
Should clipboard-write permission be removed too? w3c/clipboard-apis#163 (6 comments by @hamishwillee, @robertknight, @saschanaz, @snianu)
-
Read Blob data for the supported formats on-demand during getType. w3c/clipboard-apis#191 (3 comments by @evanstade, @snianu)
-
`supports` should take a dictionary instead of a DOMString as argument for readability w3c/clipboard-apis#211 (1 comment by @annevk)
-
-
1 pull request received 1 new comment.
w3c/edit-context
-
3 issues opened.
-
Spec defines 'double' in a way that collides with WebIDL w3c/edit-context#89, by @hober.
-
Should selection start/end be limited to the size of the text? w3c/edit-context#88, by @dandclark.
-
Spec clarifications for use with canvas vs "normal" DOM elements w3c/edit-context#86, by @dandclark.
-
-
4 issues received 7 new comments.
-
Spec defines 'double' in a way that collides with WebIDL w3c/edit-context#89 (2 comments by @dandclark)
-
Should selection start/end be limited to the size of the text? w3c/edit-context#88 (2 comments by @dandclark)
-
The timing of "deactivate an EditContext" when `HTMLElement.editContext` is replaced with another one or `null` w3c/edit-context#75 (2 comments by @dandclark, @masayuki-nakano)
-
Handling 'backwards' selection direction in an EditContext implementation w3c/edit-context#81 (1 comment by @dandclark)
-
-
1 pull request opened.
-
Allow backwards selection w3c/edit-context#87, by @dandclark.
-
-
1 pull request merged.
-
Allow backwards selection w3c/edit-context#87.
-
w3c/editing
-
1 issue opened.
-
Support navigator.clipboard inside of Service Workers w3c/editing#458, by @patrickkettner.
-
-
2 issues received 10 new comments.
-
Delayed clipboard rendering API shape. w3c/editing#423 (7 comments by @saschanaz, @smaug----, @snianu)
-
[Delayed Clipboard Rendering] Privacy issue while reading data for web custom types w3c/editing#439 (3 comments by @annevk, @snianu)
-
w3c/input-events
-
1 issue opened.
-
Update intention for insertReplacementText to include writing suggestions w3c/input-events#150, by @sanketj.
-
-
1 issue closed.
-
Update intention for insertReplacementText to include writing suggestions w3c/input-events#150.
-
-
2 issues received 7 new comments.
-
getTargetRanges of `beforeinput` differ between browsers (should not happen in EditContext) w3c/input-events#146 (5 comments by @dandclark, @johanneswilm, @masayuki-nakano, @smaug----)
-
Update intention for insertReplacementText to include writing suggestions w3c/input-events#150 (2 comments by @johanneswilm, @sanketj)
-
-
1 pull request merged.
-
Update intention for insertReplacementText to include writing suggestions w3c/input-events#149.
-
w3c/virtual-keyboard
-
1 issue opened.
-
hide() method not working in manual mode on Android (Chrome) w3c/virtual-keyboard#23, by @bschraml.
-