Re: [w3c/uievents] Event order between "compositionend" and "input" (#202)

Thanks for following up on this.

> But it doesn't seem (to me) like it's very common to need to distinguish between input events that are inside or outside composition. The vast majority of devs won't care.
> 
>     I disagree. @masayuki-nakano has already indicated that it is common to make this distinction in Firefox source.
> 
> But needing to make this distinction in FF code isn't a good reason to expose this to the web platform.

Yes, sorry, by FF code I meant Firefox front-end code, i.e. the JS used for the FF user interface. While it's not entirely representative of typical Web content, for the purposes of handling input events I think it's reasonably close.

> Would it be sufficient to phrase this as something like:
> "During composition, the isComposing attribute should be true for all input events except for the final one that updates the DOM."

I'm not familiar with the correct terminology here but that seems to match the intention at least. @masayuki-nakano does this sound right? The idea behind this language is that it then covers the cancel case too.

> Does the final beforeinput event need to have isComposing set in the same manner? My instinct is "yes, it should", but I'm open to arguments why is doesn't need to be.

@masayuki-nakano what do you think about this? ↑

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/202#issuecomment-413429238