[Bug 23422] Adding a method to deliver editing-related events to a DOM element

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23422

--- Comment #4 from Takayoshi Kochi <kochi@google.com> ---
(In reply to Ojan Vafai from comment #3)
> > > What are the cases where the request would fail?
> > 
> > For example, an element embedding a plugin (notably Flash), which
> > user agents handle specially, may not be eligible for forwarding the
> > input events, as far as I can imagine, but such a case may be ignorable.
> 
> The same argument applies to addEventListener('click') on such an element,
> right? It seems better to me to not make this a "request" style API. How
> about enableEditingEvents?

Thanks for the suggestion, it sounds good to me.

Then do

  * enableEditingEvents()
  * disableEditingEvents()

sound good to you?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 4 October 2013 08:05:57 UTC