[Webkit-unassigned] [Bug 26526] Add support for input events (oninput) to contentEditable elements

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 13 03:22:46 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=26526





--- Comment #10 from MORITA Hajime <morrita at google.com>  2010-05-13 03:22:43 PST ---
Hi James, thank you for your feedback!

(In reply to comment #9)
> Why is the event dispatching guarded by an if(renderer()) guard?
"input" event from other than contentEditable (i.e. <input> and <textarea>) is 
Because other code where handle webkitEditableContentChangedEvent does such as 
TMLFormControlElement.cpp such, I followed the same manner.
I think it is safer to check this because webkitEditableContentChangedEvent is fired inside renderer, 
and is aimed to be handled by visible elements, only which can trigger an user interaction.

But this isn't a strong opinion.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list