manhcodedao / jquery-watermark

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

Problem with jquery 1.5+ #57

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Upgrade to Jquery 1.5.2
2. Somewhere in your code use: $("#Textbox").val("anyvalue");
3. You will have an error about a syntax issue

What is the expected output? What do you see instead?
I expect it to work. I removed the watermark plugin and it worked as it used to 
be.

What version of the product are you using? On what operating system?
watermark: 3.1.3
jquery: 1.5.2

Please provide any additional information below.

Original issue reported on code.google.com by charles....@gmail.com on 3 Apr 2011 at 12:59

GoogleCodeExporter commented 8 years ago
I downgraded to watermark 3.1.2 and it works fine

Original comment by charles....@gmail.com on 3 Apr 2011 at 1:01

GoogleCodeExporter commented 8 years ago
You'll have to post a link to a test page, because I tested jQuery 1.5.2 with 
the demo page, and everything works great in all the browsers I tested. 
[Chrome, FF, IE9, IE8]

If you look at the bottom of the demo page, you will see a test of both setting 
and getting with .val().

Be sure you are testing on a stripped-down page to ensure that you don't have 
other code from you or someone else that is the cause of the problem.

Original comment by t...@speednet.biz on 3 Apr 2011 at 3:22

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I have uploaded a new demo page in the source repository (browse the source 
trunk and you can download it).  The new demo page uses jQuery 1.5.2, and adds 
a new non-watermarked element to demonstrate that .val() is not broken with 
both watermarked and non-watermarked elements.

I'll leave this issue open a little while longer in case you can come up with a 
demo page that shows it is broken.

Original comment by t...@speednet.biz on 3 Apr 2011 at 3:44

GoogleCodeExporter commented 8 years ago
I have invalidated this issue because the reported bug could not be duplicated, 
and there is no response from the person reporting it.

If anyone would like to demonstrate the reported issue, I will be happy to look 
into it further.

Original comment by t...@speednet.biz on 6 Apr 2011 at 12:53