[Bug 25683] Document "unsafe to dispatch events" in D3E if it's possible

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

--- Comment #6 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(In reply to Masayuki Nakano from comment #5)
> (In reply to Travis Leithead [MSFT] from comment #4)
> > 1. If target of the beforeinput event is beforeinput-locked, then abort;
> 
> If browsers do so, it could break compatibility with some browsers which
> don't support "beforeinput" since such browsers don't need to check it and
> may allow text input at that time.

A valid concern; I don't believe anyone implements beforeinput yet, so these
behavioral differences may not be a concern. If browsers add it, yes it could
change behavior for users, but adds the functionality.


> > Also note: the algorithm only locks one element at a time, so it's possible
> > to have "input transfer" scenarios, where your beforeinput handler catches
> > the input in order to redirect it into another input box or contenteditable.
> 
> Did you mean that "beforeinput-locked" is document or window wide state?

I expect the "beforeinput-locked" flag to be per-element.

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

Received on Wednesday, 28 May 2014 01:04:45 UTC