On Tue, Sep 29, 2009 at 11:43 PM, Ian Hickson i...@hixie.ch wrote:
So add 'multiple' on all of those and you'll have a good reason you'd
want them all to be able to wrap over multiple lines. I.e. ability to
enter multiple bank numbers, multiple social security numbers or
multiple
On Mon, 31 Aug 2009, Jonas Sicking wrote:
On Mon, Aug 31, 2009 at 12:04 AM, Ian Hicksoni...@hixie.ch wrote:
On Sun, 30 Aug 2009, Jonas Sicking wrote:
Ok, addresses might not be the best example. I would imagine that
most use cases for pattern for a single line, carries over if you
On Tue, Aug 25, 2009 at 4:24 PM, Aryeh Gregorsimetrical+...@gmail.com wrote:
For that matter, it might be nice if some patterns just refused to let
you enter anything that doesn't meet the pattern -- but not all,
clearly. E.g., [ -~]* to restrict to ASCII would really like to
just not let you
On Wed, Aug 26, 2009 at 10:18 AM, Max Romantschukm...@romantschuk.fi wrote:
I think it's important not to forget that a great deal of web applications
are internal applications not exposed to the Internet. In an environment
like that performance issues with evaluating regexps against a large
On Thu, Sep 3, 2009 at 8:07 PM, timelesstimel...@gmail.com wrote:
Si no halas ustedes Español podria visitar al: http://translate.google.com/t
How embarrassing, I fixed the typo elsewhere:
Si no hablas ustedes Español podria visitar al: http://translate.google.com/t
On Sun, Aug 30, 2009 at 10:42 PM, Jonas Sickingjo...@sicking.cc wrote:
The difference between input type=text and textarea is mostly a
rendering one. One scrolls the text when it can't fit, the other
wraps.
input type=text also can't contain newlines.
Of course, another solution would be to
On Sun, 30 Aug 2009 03:44:26 +0200, Ian Hickson i...@hixie.ch wrote:
On Tue, 25 Aug 2009, Anne van Kesteren wrote:
Also, maxlength cannot be enforced as client-side validation requirement
due to compatibility issues.
I thought we had worked around that with the dirty value flag?
I
On Sun, 30 Aug 2009, Jonas Sicking wrote:
Ok, addresses might not be the best example. I would imagine that most
use cases for pattern for a single line, carries over if you want to
have that single line wrap and be displayed as multiple lines. So if you
can provide the list of use cases
On Mon, Aug 31, 2009 at 12:04 AM, Ian Hicksoni...@hixie.ch wrote:
On Sun, 30 Aug 2009, Jonas Sicking wrote:
Ok, addresses might not be the best example. I would imagine that most
use cases for pattern for a single line, carries over if you want to
have that single line wrap and be displayed
On Wed, 19 Aug 2009, Alex Vincent wrote:
I'm drifting into writing code for the pattern attribute on text fields
again, and I wondered:� if text inputs can have pattern attribute for
regular expression matching, why not text area elements?
Lack of compelling use cases.
On Wed, 19 Aug
On Sat, Aug 29, 2009 at 9:44 PM, Ian Hicksoni...@hixie.ch wrote:
On Wed, 19 Aug 2009, Mike Shaver wrote:
It's also pretty common to enter multiple email addresses or tracking
numbers or URLs one-per-line for batch operations on sites, and they
would benefit from having client-side validation
On Sat, 29 Aug 2009, Mike Shaver wrote:
On Sat, Aug 29, 2009 at 9:44 PM, Ian Hicksoni...@hixie.ch wrote:
On Wed, 19 Aug 2009, Mike Shaver wrote:
It's also pretty common to enter multiple email addresses or tracking
numbers or URLs one-per-line for batch operations on sites, and they
Smylers wrote:
The point is to have cases specifically _for_ it -- not adding
everything for which there isn't a reason against.
If textarea pattern=... wouldn't in practice be used by authors then
there's no point in adding it. If it would be used then it should be
trivial to show some places
On Tue, Aug 25, 2009 at 3:05 AM, Anne van Kesterenann...@opera.com wrote:
Also, maxlength cannot be enforced as client-side validation requirement due
to compatibility issues.
Hmm, I hadn't thought of that. You're right, that would provide
somewhat inconsistent behavior. On the other hand,
On Tue, Aug 25, 2009 at 3:05 AM, Anne van Kesterenann...@opera.com
wrote:
Also, maxlength cannot be enforced as client-side validation
requirement due to compatibility issues.
Hmm, I hadn't thought of that. You're right, that would provide
somewhat inconsistent behavior. On the other hand,
On Tue, Aug 25, 2009 at 12:05 AM, Anne van Kesteren ann...@opera.comwrote:
Also, maxlength cannot be enforced as client-side validation requirement
due to compatibility issues.
I don't grasp what you're saying here. Are you saying that maxlength or
ValidityState.tooLong() cannot be
On Tue, 25 Aug 2009 18:57:59 +0200, Peter Kasting pkast...@google.com
wrote:
On Tue, Aug 25, 2009 at 12:05 AM, Anne van Kesteren
ann...@opera.comwrote:
Also, maxlength cannot be enforced as client-side validation requirement
due to compatibility issues.
I don't grasp what you're saying
Mike Shaver wrote:
It's also pretty common to enter multiple email addresses or tracking
numbers or URLs one-per-line for batch operations on sites, and they
would benefit from having client-side validation of such patterns.
I also believe that it would be beneficial to have an option to
Aryeh Gregor writes:
On Wed, Aug 19, 2009 at 11:32 AM, Geoffrey Sneddongsned...@opera.com
wrote:
What's the use-case for it? Textareas are almost always for such
large amounts of input that they are almost always free-form text.
Why allow the pattern attribute?
You could impose a
Smylers wrote:
Are there currently sites using JavaScript to perform the above checks
pre-submission?
The point is to have cases specifically _for_ it -- not adding
everything for which there isn't a reason against.
If textarea pattern=... wouldn't in practice be used by authors then
On Mon, Aug 24, 2009 at 9:08 AM, Chris Taylor chris.tay...@figureout.comwrote:
It's been mentioned before about limiting the length of text permissible in
a textarea element, specifically for forums.
textarea is defined to support maxlength already (
2009/8/24 Peter Kasting pkast...@google.com:
I think pattern is significantly less valuable than maxlength, but it
wouldn't be too difficult to add support for it. I vote weakly against.
More than that I'm a little concerned about potential performance
drawbacks: having a pattern to be
On Mon, Aug 24, 2009 at 6:04 AM, Max Romantschukm...@romantschuk.fi wrote:
I really don't see a case for not allowing pattern for a textarea. The
implementation side should not be that different from the same attribute on
a text input? Except for the client side overhead of parsing a large
On Mon, Aug 24, 2009 at 11:22 AM, Smylerssmyl...@stripey.com wrote:
Are there currently sites using JavaScript to perform the above checks
pre-submission?
There are many sites that use server-side checks for those purposes.
For instance, almost any site running the popular vBulletin forum
I'm drifting into writing code for the pattern attribute on text
fields again, and I wondered: if text inputs can have pattern
attribute for regular expression matching, why not text area elements?
The HTML 5 spec says: The textarea element represents a multiline
plain text edit control for the
Alex Vincent wrote:
I'm drifting into writing code for the pattern attribute on text
fields again, and I wondered: if text inputs can have pattern
attribute for regular expression matching, why not text area elements?
What's the use-case for it? Textareas are almost always for such large
On Wed, Aug 19, 2009 at 11:32 AM, Geoffrey Sneddongsned...@opera.com wrote:
What's the use-case for it? Textareas are almost always for such large
amounts of input that they are almost always free-form text. Why allow the
pattern attribute?
You could impose a minimum character length for posts
On Wed, Aug 19, 2009 at 8:32 AM, Geoffrey Sneddongsned...@opera.com wrote:
Alex Vincent wrote:
I'm drifting into writing code for the pattern attribute on text
fields again, and I wondered: if text inputs can have pattern
attribute for regular expression matching, why not text area elements?
2009/8/19 Jonas Sicking jo...@sicking.cc:
So for the pattern attribute, a use case would be on a site that
accepts US addresses (for example a store that only ships within the
US), the site could use a textarea together with a pattern that
matches US addresses.
That would be a most unusual
On Wed, Aug 19, 2009 at 2:38 PM, Jonas Sickingjo...@sicking.cc wrote:
So for the pattern attribute, a use case would be on a site that
accepts US addresses (for example a store that only ships within the
US), the site could use a textarea together with a pattern that
matches US addresses.
30 matches
Mail list logo
