Web Editing Working Group - Activity
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.