Re: [whatwg] Constraint validation for maxlength
On Sun, Jul 25, 2010 at 12:45 AM, Mounir Lamouri wrote: > I suppose, like @required, as long as it doesn't break too many > websites, we can count on evangelism teams and user feedbacks to fix > there websites. Excuse me, but I've watched Evangelism struggle and fail for 10 years. There are a number of WAP sites serving "xhtml" which doesn't properly quote attributes or escape & in urls from referrer fields. These are major news sites (no one else uses xhtml). And note that by watching, I don't mean that I was purely passive. > Removing the current behavior because some (minors?) websites are > misusing it would be sad. More useless gunk which user agents will have to work around later because evangelism doesn't work isn't something I'd like to sign up for. The current discussion about MIME types for Video is an amusing repeat of the fact that Evangelism doesn't work. And that's w/ a limited number of targets.
Re: [whatwg] Constraint validation for maxlength
On 07/24/2010 08:46 AM, Ola P. Kleiven wrote: > On Sat, 24 Jul 2010 00:21:10 +0200, Aryeh Gregor > wrote: > >> On Thu, Jul 22, 2010 at 5:46 PM, Jonas Sicking wrote: >>> I think that depends largely on how many, and how big, sites are >>> affected by this. Do you have a list of known sites with this issue? >> >> No, I was just raising the issue to see what people thought. Maybe >> someone from Opera could share a reason why they don't follow the spec >> here, unless the spec was different when they implemented it or >> something. > > From what I can see this was changed in Opera four years ago after some > debate [1]. The big problem was pre- and script-filled fields that > exceeded maxlength. Users got confused when fields they hadn't touched > threw an error. See also [2] and [3] > > Sites that broke back then were: (I don't know know if any of them still > are affected, many require login) > > The YaBB forum software > SuperOffice eJournal (a support system Opera used) > http://kayak.com/ (was fixed after we pointed it out) > http://www.costco.com/ (internal navigation) > http://www.nowwhere.com.au (zooming maps) > http://www.zap2it.com > http://www.kwick.de/forum > > 1) https://bugs.opera.com/browse/DSK-151609 (sorry, Opera access only) > 2) > http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2006-February/005695.html > > 3) > http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2006-January/005459.html I suppose, like @required, as long as it doesn't break too many websites, we can count on evangelism teams and user feedbacks to fix there websites. Removing the current behavior because some (minors?) websites are misusing it would be sad. -- Mounir
Re: [whatwg] Constraint validation for maxlength
On Sat, 24 Jul 2010 00:21:10 +0200, Aryeh Gregor wrote: On Thu, Jul 22, 2010 at 5:46 PM, Jonas Sicking wrote: I think that depends largely on how many, and how big, sites are affected by this. Do you have a list of known sites with this issue? No, I was just raising the issue to see what people thought. Maybe someone from Opera could share a reason why they don't follow the spec here, unless the spec was different when they implemented it or something. From what I can see this was changed in Opera four years ago after some debate [1]. The big problem was pre- and script-filled fields that exceeded maxlength. Users got confused when fields they hadn't touched threw an error. See also [2] and [3] Sites that broke back then were: (I don't know know if any of them still are affected, many require login) The YaBB forum software SuperOffice eJournal (a support system Opera used) http://kayak.com/ (was fixed after we pointed it out) http://www.costco.com/ (internal navigation) http://www.nowwhere.com.au (zooming maps) http://www.zap2it.com http://www.kwick.de/forum 1) https://bugs.opera.com/browse/DSK-151609 (sorry, Opera access only) 2) http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2006-February/005695.html 3) http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2006-January/005459.html -- Ola P. Kleiven Core Compatibility PM Opera Software
Re: [whatwg] Constraint validation for maxlength
On Thu, Jul 22, 2010 at 5:46 PM, Jonas Sicking wrote: > I think that depends largely on how many, and how big, sites are > affected by this. Do you have a list of known sites with this issue? No, I was just raising the issue to see what people thought. Maybe someone from Opera could share a reason why they don't follow the spec here, unless the spec was different when they implemented it or something.
Re: [whatwg] Constraint validation for maxlength
On Thu, Jul 22, 2010 at 2:18 PM, Aryeh Gregor wrote:
> maxlength predates all the other form validation attributes by many
> years. Historically, browsers would prohibit users from entering text
> beyond the maxlength of an input or textarea, but would not prohibit
> form submission. HTML5 changes this:
>
> """
> Constraint validation: If an element has a maximum allowed value
> length, and its dirty value flag is true, and the code-point length of
> the element's value is greater than the element's maximum allowed
> value length, then the element is suffering from being too long.
> """
> http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#limiting-user-input-length
>
> If I read it correctly, this means that pages that previously worked
> no longer will, if a script sets the value of the input to something
> longer than the maxlength. Something like this was reported against
> Chromium (although in this case it was more of a browser bug for
> autofilling passwords beyond maxlength):
>
> http://code.google.com/p/chromium/issues/detail?id=45640#c2
>
> These two test cases show that Opera maintains the legacy behavior
> (not compatible with the spec) and submits the forms regardless of
> maxlength violations, while WebKit (Chromium) blocks submission as
> required by the spec:
>
> data:text/html, onload="document.getElementById('a').value='foo'"> maxlength=2>Try to submit the form
>
> data:text/html, type=submit> onclick="document.getElementById('a').maxLength = 2; return
> false">Enter "foo" into the input, click here, then try to submit
>
> Should the spec (and WebKit) be changed here, or should Opera change?
I think that depends largely on how many, and how big, sites are
affected by this. Do you have a list of known sites with this issue?
/ Jonas
[whatwg] Constraint validation for maxlength
maxlength predates all the other form validation attributes by many years. Historically, browsers would prohibit users from entering text beyond the maxlength of an input or textarea, but would not prohibit form submission. HTML5 changes this: """ Constraint validation: If an element has a maximum allowed value length, and its dirty value flag is true, and the code-point length of the element's value is greater than the element's maximum allowed value length, then the element is suffering from being too long. """ http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#limiting-user-input-length If I read it correctly, this means that pages that previously worked no longer will, if a script sets the value of the input to something longer than the maxlength. Something like this was reported against Chromium (although in this case it was more of a browser bug for autofilling passwords beyond maxlength): http://code.google.com/p/chromium/issues/detail?id=45640#c2 These two test cases show that Opera maintains the legacy behavior (not compatible with the spec) and submits the forms regardless of maxlength violations, while WebKit (Chromium) blocks submission as required by the spec: data:text/html,Try to submit the form data:text/html,Enter "foo" into the input, click here, then try to submit Should the spec (and WebKit) be changed here, or should Opera change?
