diff --git a/meetings/16-09-22TPAC-3.md b/meetings/16-09-22TPAC-3.md index 3616fa3..9b13924 100644 --- a/meetings/16-09-22TPAC-3.md +++ b/meetings/16-09-22TPAC-3.md @@ -32,7 +32,7 @@ This meeting will take place on 22 September 2016 as part of [TPAC 2016](https:/ Proposed solution: Add a method to this beforeinput event to revert the dom changes caused by the composition so that the DOM changes can be reverted before JS handling of composition insert [3]. Other ideas? -* After the F2F in San Francisco, it was argued on the part of the Chrome team that the clipboard-related beforeinput events should only deal with dom-insertion and not with clipboard manipulation. These changes have been put inot the spec draft. In that connection it was also argued that possible the history-stack-related beforeinput event spossibly could be decoupled from the history stack. This would be somewhat different from the discussion at the F2F where the majority argued that the browser-internal history stack is unusable as soon as JS handles at least some types of editing operations. Is this something we need to reformulate in the spec, or does it not really matter, as undo/redo will have to be handled by JS anyway as long as JS preventDefaults some beforeinput events? [4] +* After the F2F in San Francisco, it was argued on the part of the Chrome team that the clipboard-related beforeinput events should only deal with dom-insertion and not with clipboard manipulation. These changes have been put into the spec draft. In that connection it was also argued that possible the history-stack-related beforeinput events possibly could be decoupled from the history stack. This would be somewhat different from the discussion at the F2F where the majority argued that the browser-internal history stack is unusable as soon as JS handles at least some types of editing operations. Is this something we need to reformulate in the spec, or does it not really matter, as undo/redo will have to be handled by JS anyway as long as JS preventDefaults some beforeinput events? [4] * Static Range - finish first draft spec, need to make it official. [Proposal](https://github.com/garykac/staticrange/blob/master/staticrange.md)