- From: <bugzilla@jessica.w3.org>
- Date: Tue, 13 Mar 2012 18:36:24 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12958 --- Comment #11 from Aryeh Gregor <ayg@aryeh.name> 2012-03-13 18:36:21 UTC --- (In reply to comment #9) > I think command and value make perfect sense for textInput as well. "value" > would replace textInput's current "data" property and "command" would replace > the "inputMethod" property. > > As I've said on the mailing list, the list of inputMethods should be truncated > to not include things like "handwriting", "multimodal" and "option". They > should be a strict subset of the commands used for beforeInput/input events. I think it's confusing to overload .command and .value like that. I'd make a new BeforeInputEvent or TextBeforeInputEvent interface and add appropriately-named properties like .newValue. You definitely want to have the beforeinput event for text inputs expose the new value, otherwise there's not much point. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 13 March 2012 18:36:33 UTC