search

google-code-export / jquery-watermark

Automatically exported from code.google.com/p/jquery-watermark
1 stars 0 forks source link

Unable to bind 'change' event, when type=password #100

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. http://jsfiddle.net/g3T32/

What is the expected output? What do you see instead?
Expected to work

What version of the product are you using? On what operating system?
3.1.4.

Please provide any additional information below.
By removing `useNative: false` - the issue goes away, but only for 
FF/Chrome/Opera, IE still fails to bind an event.

Original issue reported on code.google.com by ra...@angarka.ru on 19 Dec 2012 at 2:26

GoogleCodeExporter commented 9 years ago 
This is expected behavior, as the password element is replaced when showing a 
watermark.  Please read the documentation.

Original comment by t...@speednet.biz on 19 Dec 2012 at 1:56

GoogleCodeExporter commented 9 years ago 
I did see that in the first place:

"Avoid programmatic changes to passwords - Because of the complexity of making 
password watermarks operate..."

But it comes as recommendation. =)
This really makes a pain in the ass to run js match() on the password field to 
show user - requirements for the password length before submitting form. Many 
websites come with this feature. Any workaround to this?

Thanks.

Original comment by ra...@angarka.ru on 19 Dec 2012 at 4:23

GoogleCodeExporter commented 9 years ago 
If you are checking the length of the password when the form is submitted, then 
why would you be trying to hook the onchange event?  You're not doing what you 
say you want to do.  I can't really assist with basic coding stuff.  You should 
be hooking the form's submit event.

Again, this is not a bug of the plugin, this is a coding issue on your page.

Original comment by t...@speednet.biz on 19 Dec 2012 at 5:31

GoogleCodeExporter commented 9 years ago 
What do you think I'm doing? In that jsfiddle you can clearly see that i'm 
hooking up onchange event. No need to act this way telling me that I don't know 
basic coding stuff. The problem resolved by hooking up 'live' event.

Original comment by ra...@angarka.ru on 19 Dec 2012 at 5:41

GoogleCodeExporter commented 9 years ago 
Oh my goodness, you did not read my message.  For the second time, you should 
not be hooking up to the onchange event.  This is NOT a coding help forum.  
This is for bug reports.  There is no bug here.

Original comment by t...@speednet.biz on 19 Dec 2012 at 7:00