On Sat, 28 Aug 2010 03:16:16 +0200, Ojan Vafai o...@chromium.org wrote:
WebKit has added the input event to contentEditable nodes. That part of
this proposal seemed non-controversial. Do other browser vendors support
changing the description of this event to apply to contentEditable nodes
WebKit has added the input event to contentEditable nodes. That part of this
proposal seemed non-controversial. Do other browser vendors support changing
the description of this event to apply to contentEditable nodes as well?
Ojan
On Wed, Jun 16, 2010 at 5:33 PM, Ojan Vafai o...@chromium.org
We've given this a bit more thought and come the the conclusion that
textInput basically does what we want out of beforeInput, except that it
doesn't currently fire for actions like undo/redo. So, basically, we're
proposing that textInput should fire for any DOM modifying event and,
ideally, that
On Wed, Mar 3, 2010 at 6:44 PM, Boris Zbarsky bzbar...@mit.edu wrote:
So I have to ask... Why are events _before_ the edit needed?
If we add these, then you have to define what happens when those event
handlers modify the state of the DOM in arbitrary ways, including carrying
out operations
On 3/4/10 4:11 AM, Ojan Vafai wrote:
WebKit would like to implement this in the (very) near future. Before
proceeding, we'd like to hear from other browser vendors that you're
roughly on board with this direction of adding beforeinput and input events.
Here are the changes I can think of that
WebKit would like to implement this in the (very) near future. Before
proceeding, we'd like to hear from other browser vendors that you're roughly
on board with this direction of adding beforeinput and input events.
Here are the changes I can think of that would result from this:
1) Fire input
On 3/3/10 9:31 PM, Daniel Danilatos wrote:
Worth noting, the events should convey the user intent - so, e.g. not
just delete chars 5 - 8 but forward word delete, which is chars 5 -
8.
So I have to ask... Why are events _before_ the edit needed?
If we add these, then you have to define what
On Tue, 23 Jun 2009, Ojan Vafai wrote:
Currently, textareas and text inputs support the oninput event that
fires on all user-initiated modifications to their content. We should
add this event to contentEditable elements as well and add an action
property the specifies what action the user
On 6/24/09 4:42 AM, Ojan Vafai wrote:
SUMMARY
Currently, textareas and text inputs support the oninput event
The event is input ;)
that
fires on all user-initiated modifications to their content. We should
add this event to contentEditable elements as well and add an action
property the
On Tue, 23 Jun 2009 21:42:18 -0400, Ojan Vafai o...@chromium.org wrote:
SUMMARY
Currently, textareas and text inputs support the oninput event that
fires
on all user-initiated modifications to their content. We should add this
event to contentEditable elements as well and add an action
On Wed, Jun 24, 2009 at 6:41 PM, Michael A. Puls IIshadow2...@gmail.com wrote:
On Wed, 24 Jun 2009 11:49:27 -0400, Anne van Kesteren ann...@opera.com
wrote:
By the way, did anyone ever implement textInput from DOM Level 3 Events?
Just Webkit.
And Mozilla ?
On 6/24/09 6:49 PM, Anne van Kesteren wrote:
On Wed, 24 Jun 2009 12:21:41 +0200, Olli Pettay
olli.pet...@helsinki.fi wrote:
Why would you need paste? There is paste event
(though, not properly specified anywhere, I think);
I'd think you want an event that covers all editing actions. Also,
Michael A. Puls II wrote:
And Mozilla ?
https://developer.mozilla.org/En/DOM_Events#textInput
I tested it on a textarea in Firefox latest trunk before posting. It
didn't fire.
Yeah, that documentation was apparently authored by copy/paste from the
spec...
Fixed it to make it clear that
On Wed, Jun 24, 2009 at 11:51 AM, Olli Pettay olli.pet...@helsinki.fiwrote:
On 6/24/09 6:49 PM, Anne van Kesteren wrote:
On Wed, 24 Jun 2009 12:21:41 +0200, Olli Pettay
olli.pet...@helsinki.fi wrote:
Why would you need paste? There is paste event
(though, not properly specified anywhere, I
SUMMARY
Currently, textareas and text inputs support the oninput event that fires
on all user-initiated modifications to their content. We should add this
event to contentEditable elements as well and add an action property the
specifies what action the user took that caused the input event.
We
15 matches
Mail list logo
