<div class="gmail_quote">On Wed, Jun 24, 2009 at 11:51 AM, Olli Pettay <span dir="ltr"><<a href="mailto:Olli.Pettay@helsinki.fi" target="_blank">Olli.Pettay@helsinki.fi</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div>On 6/24/09 6:49 PM, Anne van Kesteren wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, 24 Jun 2009 12:21:41 +0200, Olli Pettay<br>
<<a href="mailto:Olli.Pettay@helsinki.fi" target="_blank">Olli.Pettay@helsinki.fi</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Why would you need "paste"? There is "paste" event<br>
(though, not properly specified anywhere, I think);<br>
</blockquote>
<br>
I'd think you want an event that covers all editing actions. Also,<br>
that's what the input event does for <input>.<br>
<br>
By the way, did anyone ever implement textInput from DOM Level 3 Events?<br>
If not maybe someone should email www-dom about "nuking" that. </blockquote></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
</blockquote></div></div>
Why would you want to nuke textInput? Perhaps textInput (in some extended form) could be used for contentEditable and we could deprecate<br>
input event. textInput has the advantage that it has .data</blockquote><div><br></div><div>textInput only fires when you input text. It does not fire when you delete, paste, bold (i.e. ctrl+b), etc.</div>
<div><br></div><div>That does make me wonder whether certain input events should have a data property (i.e. action=inserttext). It's a little ugly to just have data in some cases, but it's no more ugly than rich text libraries needing to listen to input+textInput or input+keydown.</div>
<div><br></div><div>On the other hand, maybe it we should try to spec data for all input event cases.</div><div><br></div><div>Ojan</div></div>