Thank you for the reply. > Anyway, do you have any concern about the behaviors of the current browsers?
No, not as of now particularly. Neither I know how UAs are going to implement "require that authors not let authors enter values longer than the maxlength" behavior, sorry for the ignorance. I just worried since I saw some applications in the past that don't allow users to enter values longer than the maxlength, and some of them were unusable with CJK input methods. If you're going to change the definition to "not to allow entering values longer than the maxlength," I wish it be clearly defined with international environment in mind where text may be shorten as user types, and therefore they must allow longer values than maxlength during the undetermined state. Transition from undetermined to determined could be kicked by several criteria and it's hard to control, so my gut feeling is that "not allowing entering longer values than maxlength" tends to result poor in CJK, but I'm fine as long as it was designed such conditions in mind. Regards, Koji From: tk...@google.com [mailto:tk...@google.com] On Behalf Of TAMURA, Kent Sent: Friday, March 25, 2011 1:07 PM To: Koji Ishii Cc: wha...@whatwg.org Subject: Re: [whatwg] Constraint validation feedback (various threads) On Thu, Mar 24, 2011 at 13:37, Koji Ishii <kojii...@gluesoft.co.jp<mailto:kojii...@gluesoft.co.jp>> wrote: Does that cover the case where multiple characters can be composed to single character? I'm thinking the case where undetermined text in CJK input methods tends to be longer and may be shortened once determined, but there may be more cases where text gets shorter as you type. Ishii-san, It's not related to this thread. Anyway, do you have any concern about the behaviors of the current browsers? -- TAMURA Kent Software Engineer, Google
