Jörn Zaefferer schrieb:
Glen Lipka schrieb:
Would this work onKeyPress? I think I get where you are going.
Struggling. :(
Sure, just apply the validator on keypress:
$(form input).keypress(function() {
$(this).validate();
});
I you have ideas to make the plugin easier to use,
Hey Klaus
And the using it like this:
input validate=pattern:###-###-## /
And I still vote for doing in a standards compliant way...
As an alternative, you can still do it standards-compliant (or write an XHTML
module):
input class=$v(pattern:###-###-##) /
The plugin checks the
Here's an idea:
label for=foo class=validate 000h000h00/label
input name=foo id=foo type=text /
It's HTML 4.01, will probably pass for strict, and it semantically
separates the validation from the field. The idea is that for every label
with class validate, there's a validation mask somewhere
I don't think that, technically, things like parens and colons are
permitted in a class.
As an alternative, you can still do it standards-compliant (or write an
XHTML module):
input class=$v(pattern:###-###-##) /
The plugin checks the class if there is no validate attribute.
-- Jörn
After checking the W3C spec, it doesn't say much about what is and isn't
legal in a class in HTML. It simply says that it's a CDATA. But, the
examples in the spec doc do allow hyphens. I'd be cautious about what
characters I use in a class, because CSS is stricter about what may be in
a
Brian schrieb:
After checking the W3C spec, it doesn't say much about what is and isn't
legal in a class in HTML. It simply says that it's a CDATA. But, the
examples in the spec doc do allow hyphens. I'd be cautious about what
characters I use in a class, because CSS is stricter about what
Brian schrieb:
Here's an idea:
label for=foo class=validate 000h000h00/label
input name=foo id=foo type=text /
*snip*
What do you think? I'm almost feeling crazy enough to take a whack at it.
It all starts with $(label), how hard could it be? :)
That is an interesting approach. It
Brian schrieb:
After checking the W3C spec, it doesn't say much about what is and isn't
legal in a class in HTML. It simply says that it's a CDATA. But, the
examples in the spec doc do allow hyphens. I'd be cautious about what
characters I use in a class, because CSS is stricter about what
On 9/28/06, Brian [EMAIL PROTECTED] wrote:
Here's an idea:
label for=foo class=validate 000h000h00/label
input name=foo id=foo type=text /
What about when you want to change some aspect of the mask? Say, the
phone number mask now needs to handle international numbers as well.
Why not separate
Having used the:
input class=required us-phone-number ...
method several times,,, It is definitely the way to slip the new
feature by the standards!
We can all see the simple jq code for implementing this.
And keypress always scares me (as a user not a programmer) I hate to
be told about my
I think that people are going to want more flexibility in terms of what
they want to validate. It would be great to include very common
shortcuts, like us-phone-number, credit-card-number, or
email-address. But, we can't predict what everyone's data will look
like. There must be a way to
for the jQ soultuon :
1 class to mention which plugin will handle the validations
1 or more other classes as defined in that plugin
we bind early on all fields that have the 'plugin' class, then we can
easily handle flipping from US-phone-number to UK-phone-number.. etc!
how the formats are
Ⓙⓐⓚⓔ schrieb:
for the jQ soultuon :
1 class to mention which plugin will handle the validations
1 or more other classes as defined in that plugin
we bind early on all fields that have the 'plugin' class, then we can
easily handle flipping from US-phone-number to UK-phone-number.. etc!
how
As John pointed out, implementing some of the new W3C forms API might do the trick. Anyone have any particular parts of that API that might be a good place to start (validation comes to mind).-- Yehuda
On 9/27/06, Glen Lipka [EMAIL PROTECTED] wrote:
For Intuit (QuickBooks, Quicken, TurboTax). We
I saw that one one. The mask I am describing is on the phone number field. It fixes formatting on the fly using keypress. (rather than Blur)So it never shows an error, it just fixes the formatting automagically. Try typing in (510) 555-12dog12. It ends up 510-555-1212.
We are going to use
John Resig schrieb:
phone number mask.
I think this would make a great jQuery plugin. It has the right pieces of
the puzzle. Example:
input type=text jMask=###-###-
Works as a great constraint to keep data in the correct format.
I have no idea how to port this into a plugin. I am
Glen Lipka schrieb:
Would this work onKeyPress? I think I get where you are going.
Struggling. :(
Sure, just apply the validator on keypress:
$(form input).keypress(function() {
$(this).validate();
});
I you have ideas to make the plugin easier to use, just tell me .-)
-- Jörn
You can post links to whatever projects you like here, but you dont have to. Really the main reason for the mailing list is to ask for suggestions to make code better ;)On 9/26/06,
Glen Lipka [EMAIL PROTECTED] wrote:If I am working on a jQuery project, should I post url's here for people to see?
Woah - do you design for Quickbooks? That'd be hot :-)
I really like the slidey menu - hidden, but useful, navigation.
--John
On 9/26/06, Glen Lipka [EMAIL PROTECTED] wrote:
If I am working on a jQuery project, should I post url's here for people to
see?
Is it inappropriate to ask for
John! Where the heck you been man? We've missed your input here. :o)
Rey,,,
John Resig wrote:
Woah - do you design for Quickbooks? That'd be hot :-)
I really like the slidey menu - hidden, but useful, navigation.
--John
___
jQuery mailing list
He's been sick man.
From: Rey Bango
John! Where the heck you been man? We've missed your input here. :o)
Rey,,,
John Resig wrote:
Woah - do you design for Quickbooks? That'd be hot :-)
I really like the slidey menu - hidden, but useful, navigation.
--John
21 matches
Mail list logo
