- From: Johannes Wilm <notifications@github.com>
- Date: Wed, 26 Aug 2015 15:35:02 -0700
- To: w3c/editing <editing@noreply.github.com>
- Message-ID: <w3c/editing/issues/73/135196850@github.com>
Some more things I discovered: * The beforeInput event is actually mentioned in several other specs. For example here: https://w3c.github.io/uievents/#h-sync-async or https://w3c.github.io/uievents/#h-events-keyboard-event-order but with a broken link. It is described as synchronous (correctly) and I also think ti describes correctly the order of events. * At above links the beforeInput event is described as "only for keys which produce a character value". I don't think that corresponds to how we want to use that event with formatting bold, etc.. * Here it describes the InputEvent: https://developer.mozilla.org/en-US/docs/Web/API/InputEvent but the link to the specification gives us another dead link. I can see that the event was removed from that spec in January: https://github.com/w3c/uievents/commit/b2bd0cfea66b00a0fc7f25993716a3374db90beb due to a bug report by Gary Kacmarcik (Google) https://lists.w3.org/Archives/Public/www-dom/2015JanMar/0029.html .... so altogether it seems as if the beforeInput/Input events mentioned other places are earlier versions of the event we have been describing in this spec until it changed name due to the decisions of the F2F. Testing it out on Chrome and FF, it doesn't look like the input event on cE=true elements holds any information. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/73#issuecomment-135196850
Received on Wednesday, 26 August 2015 22:35:32 UTC