- From: Mounir Lamouri <mounir.lamouri@gmail.com>
- Date: Fri, 25 Mar 2011 13:26:16 +0100
On 03/25/2011 05:24 AM, Koji Ishii wrote: > 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. FWIW, I did a proposal to change how maxlength currently behaves that would fix this issue too. See: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-November/029145.html And for some clarifications: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-February/030444.html -- Mounir
Received on Friday, 25 March 2011 05:26:16 UTC