- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Oct 2011 21:50:38 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13769 --- Comment #37 from Marat Tanalin | tanalin.com <mtanalin@yandex.ru> 2011-10-24 21:50:34 UTC --- (In reply to comment #36) > (In reply to comment #34) > > > > http://foxconn.ru/company/feedback/ > > This page is a classic example of why this is silly. I was able to submit the > form with "-" as the textarea contents, which is just as useless as submitting > it with " ". It's not like I would enter blank spaces accidentally but would > not enter dashes accidentally. You are repeating yourself. I'm not going to do the same though. See comment 10 and comment 11. > Anyway, I agree with Mounir. We should start by adding this to <input > type=text>, with the behaviour just being that the value's start and end spaces > are trimmed when editing (whether this is exposed to the user is a UA issue). > Then we can see how commonly this is used and how common it is for people to do > it across an entire form or fieldset and how common it is for people to need it > for textarea, and go from there for WF4. Mounir's intention was probably just like "finally do at least something" as for trimming. As for me personally, now after your proposal to drop <time> element (bug 13240) I'm not going to be surprised at any of your decisions as for HTML5 at all. Just in case, please take into account (again) that 'trim' attribute should affect value examined by built-in client-side validation only. Trimming actual value before sending it to server is generally pointless. The only point to trim value is to inform browser to treat whitespace-only values as literally empty strings when validating according to 'required' attribute (see initial description of this bug). -- Configure bugmail: http://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 Monday, 24 October 2011 21:50:43 UTC