- From: <bugzilla@jessica.w3.org>
- Date: Tue, 08 Apr 2014 05:17:26 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25288
Bug ID: 25288
Summary: Should change the definition of InputEvent.isComposing
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: DOM3 Events
Assignee: garykac@google.com
Reporter: masayuki@d-toybox.com
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, www-dom@w3.org
Blocks: 25287
Currently, InputEvent.isComposing is defined as:
"true if the input event occurs as part of a composition session, i.e., after a
compositionstart event and before the corresponding compositionend event."
However, this behavior isn't useful at committing composition.
E.g.,
keydown: key="a", isComposing=false
compositionstart: data=something
compositionupdate: data="あ"
beforeinput: data="あ", isComposing=true
// DOM change
input: data="あ", isComposing=true
keyup: key="a", isComposing=true
keydown: key="Enter", isComposing=true
beforeinput: data="あ", isComposing=true
// DOM change
input: data="あ", isComposing=true
compositionend: data="あ"
keyup: key="Enter", isComposing=false
Web apps must want to handle the last "input" event is as not a part of
composition because the composition string is committed.
So, I think that InputEvent.isComposing should be defined as:
"true if the input event occurs as part of a composition session, i.e., after a
compositionstart event and before the corresponding compositionend event.
Additionally, there is uncommitted composition string."
I think that this definition isn't useful for KeyboardEvent.isComposing because
some Chinese IMEs don't expose composition string to applications until it's
committed. So, KeyboardEvent.isComposing should just refer compositionstart and
compositionend.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 8 April 2014 05:17:28 UTC