jquery-watermark - Project Hosting on Google Code

Last 7 days Dec 28, 2009 r31 ([No log message]) committed by t...@speednet.biz - [No log message] [No log message] Dec 28, 2009 r30 (Added logo.) committed by t...@speednet.biz - Added logo. Added logo. Dec 28, 2009 issue 12 (Page_ClientValidate('ValidationGroup') results in 'undefined...) commented on by t...@speednet.biz - I'll need more info, including a specific use-case if I am to investigate. A demo page of the problem would be best. I'll need more info, including a specific use-case if I am to investigate. A demo page of the problem would be best. Dec 28, 2009 issue 12 (Page_ClientValidate('ValidationGroup') results in 'undefined...) commented on by t...@speednet.biz - I'll need more info, including a specific use-case if I am to investigate. A demo page of the problem would be best. I'll need more info, including a specific use-case if I am to investigate. A demo page of the problem would be best. Last 30 days Dec 14, 2009 issue 12 (Page_ClientValidate('ValidationGroup') results in 'undefined...) reported by surolia.manish - Page_ClientValidate('ValidationGroup') results in 'undefined' Page_ClientValidate('ValidationGroup') results in 'undefined' Dec 10, 2009 r29 ([No log message]) committed by t...@speednet.biz - [No log message] [No log message] Earlier this year Nov 30, 2009 issue 11 (ASP.NET ValidationGroup bug) Status changed by t...@speednet.biz - FIXED in version 3.0.3 Status: Fixed FIXED in version 3.0.3 Status: Fixed Nov 30, 2009 issue 9 (Form doesn't submit in Chrome when submitting programmatical...) Status changed by t...@speednet.biz - FIXED in version 3.0.3 Status: Fixed FIXED in version 3.0.3 Status: Fixed Nov 30, 2009 jquery.watermark-3.0.3.zip (Watermark plugin for jQuery v3.0.3 (current release) ) file uploaded by t...@speednet.biz - Labels: Featured Type-Archive Labels: Featured Type-Archive Nov 30, 2009 r28 (Version 3.0.3 (2009-11-30) Solved Issue #9 (Form doesn't s...) committed by t...@speednet.biz - Version 3.0.3 (2009-11-30) Solved Issue #9 (Form doesn't submit in Chrome when submitting programmatically) - This issue only manifested itself when native watermark support was turned off in Google Chrome, and the form was submitted programmatically [by calling form.submit()]. It happened because Google Chrome (and Google Chrome alone) makes the native form.submit function invisible to JavaScript, making the ability to hijack the seemingly non-existent function very difficult. A creative solution was achieved (see the code if you're interested). Solved Issue #11 (ASP.NET ValidationGroup bug) - The issue occured because the original arguments were not being passed to the hijacked function (the ASP.NET client validation function). Fixed a potential, but unreported, issue that could arise if arguments (for some reason) were passed to the form.submit function. Version 3.0.3 (2009-11-30) Solved Issue #9 (Form doesn't submit in Chrome when submitting programmatically) - This issue only manifested itself when native watermark support was turned off in Google Chrome, and the form was submitted programmatically [by calling form.submit()]. It happened because Google Chrome (and Google Chrome alone) makes the native form.submit function invisible to JavaScript, making the ability to hijack the seemingly non-existent function very difficult. A creative solution was achieved (see the code if you're interested). Solved Issue #11 (ASP.NET ValidationGroup bug) - The issue occured because the original arguments were not being passed to the hijacked function (the ASP.NET client validation function). Fixed a potential, but unreported, issue that could arise if arguments (for some reason) were passed to the form.submit function. Nov 30, 2009 issue 9 (Form doesn't submit in Chrome when submitting programmatical...) Status changed by t...@speednet.biz - There is definitely an issue here with Chrome and using a programmiatic submit, thanks for posting the issue. The form submit function unfortunately differs widely among browsers. Some make it easy to replace, others treat it in a very "hard-coded" manner. I'll be looking into a more generic jQuery event-based approach to see if it works better for all browsers. Whatever fix I end up using, it should be part of the next release. Status: Accepted There is definitely an issue here with Chrome and using a programmiatic submit, thanks for posting the issue. The form submit function unfortunately differs widely among browsers. Some make it easy to replace, others treat it in a very "hard-coded" manner. I'll be looking into a more generic jQuery event-based approach to see if it works better for all browsers. Whatever fix I end up using, it should be part of the next release. Status: Accepted Nov 30, 2009 issue 11 (ASP.NET ValidationGroup bug) commented on by t...@speednet.biz - BTW, one small thing you (and anyone!) can do to help is to give the plugin a rating over at the jQuery site: http://plugins.jquery.com/project/jquery-watermark Thanks! BTW, one small thing you (and anyone!) can do to help is to give the plugin a rating over at the jQuery site: http://plugins.jquery.com/project/jquery-watermark Thanks! Nov 30, 2009 issue 11 (ASP.NET ValidationGroup bug) commented on by t...@speednet.biz - Awesome, thanks for testing, I'll make it part of the next release. Thanks for the props too. Awesome, thanks for testing, I'll make it part of the next release. Thanks for the props too. Nov 30, 2009 issue 11 (ASP.NET ValidationGroup bug) commented on by gerasha - Yes it works, tried couple of different scenarios. Thanks for great product. Yes it works, tried couple of different scenarios. Thanks for great product. Nov 30, 2009 issue 11 (ASP.NET ValidationGroup bug) Status changed by t...@speednet.biz - Can you try inserting a different fix to see if it works in your scenario? Please replace the line you marked "HERE IS A FIX" (the if/else) with the following: line of code. It is more generic, and should work with all functions. origFn.apply(null, Array.prototype.slice.call(arguments)); Status: Accepted Can you try inserting a different fix to see if it works in your scenario? Please replace the line you marked "HERE IS A FIX" (the if/else) with the following: line of code. It is more generic, and should work with all functions. origFn.apply(null, Array.prototype.slice.call(arguments)); Status: Accepted Nov 29, 2009 issue 10 (Watermak classname property is not working on Google Chrome) Status changed by t...@speednet.biz - You have to disable native watermark support if you want to set a class in Chrome. This fact is highlighted in the demo page, in the 3rd demonstration. Status: Invalid You have to disable native watermark support if you want to set a class in Chrome. This fact is highlighted in the demo page, in the 3rd demonstration. Status: Invalid Nov 24, 2009 issue 11 (ASP.NET ValidationGroup bug) commented on by gerasha - Here is a fix: // Hijack any functions found in the triggerFns list if (triggerFns.length) { // Wait until DOM is ready before searching $(function () { var i, name, fn; for (i=triggerFns.length-1; i>=0; i--) { name = triggerFns[i]; fn = window[name]; if (typeof(fn) === "function") { window[name] = (function (origFn) { return function () { $.watermark.hideAll(); //HERE IS A FIX if (arguments.length == 1) origFn(arguments[0]) else orifFn(); }; })(fn); } } }); } Here is a fix: // Hijack any functions found in the triggerFns list if (triggerFns.length) { // Wait until DOM is ready before searching $(function () { var i, name, fn; for (i=triggerFns.length-1; i>=0; i--) { name = triggerFns[i]; fn = window[name]; if (typeof(fn) === "function") { window[name] = (function (origFn) { return function () { $.watermark.hideAll(); //HERE IS A FIX if (arguments.length == 1) origFn(arguments[0]) else orifFn(); }; })(fn); } } }); } Nov 24, 2009 issue 11 (ASP.NET ValidationGroup bug) reported by gerasha - What steps will reproduce the problem? 1.Create blank aspx page, place this inside form1 <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox> <asp:LinkButton ID="LinkButton1" ValidationGroup="test1" runat="server">LinkButton</asp:LinkButton> <asp:CustomValidator ID="CustomValidator1" ValidationGroup="test1" runat="server" ClientValidationFunction="validateRequired" ErrorMessage="CustomValidator1" ControlToValidate="TextBox1" ValidateEmptyText="True"></asp:CustomValidator> <br /> <asp:TextBox ID="TextBox2" runat="server"></asp:TextBox> <asp:LinkButton ID="LinkButton2" ValidationGroup="test2" runat="server">LinkButton2</asp:LinkButton> <asp:CustomValidator ID="CustomValidator2" ValidationGroup="test2" runat="server" ClientValidationFunction="validateRequired" ErrorMessage="CustomValidator2" ControlToValidate="TextBox2" ValidateEmptyText="True"></asp:CustomValidator> 2. Place this script between head and body <script type="text/javascript" src="http://www.google.com/jsapi"></script> <script type="text/javascript"> google.load("jquery", "1.3.2");</script> <script type="text/javascript"> function validateRequired(oSrc, args) { var txt = $get(oSrc.controltovalidate); var pass = (args.Value.length > 0); if (pass) { $('#' + txt.id).removeClass('requirederror'); args.IsValid = true; } else { // set length css class to error. $('#' + txt.id).addClass('requirederror'); args.IsValid = false; } } </script> When you click on first link, only 1 validator execute, when you click on second link another textbox validate. It happened, because i separate them by ValidationGroup. It works as expected. Now add between header and body <script type="text/javascript" src="jquery.watermark.js"></script> And now when you click on any linkbutton validation happened for all controls. Which not suppose to be. Is any way to fix it. I dont use watermark library on my page, but its in Master page.Im using Nov 11 release. Thanks a lot for great product What steps will reproduce the problem? 1.Create blank aspx page, place this inside form1 <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox> <asp:LinkButton ID="LinkButton1" ValidationGroup="test1" runat="server">LinkButton</asp:LinkButton> <asp:CustomValidator ID="CustomValidator1" ValidationGroup="test1" runat="server" ClientValidationFunction="validateRequired" ErrorMessage="CustomValidator1" ControlToValidate="TextBox1" ValidateEmptyText="True"></asp:CustomValidator> <br /> <asp:TextBox ID="TextBox2" runat="server"></asp:TextBox> <asp:LinkButton ID="LinkButton2" ValidationGroup="test2" runat="server">LinkButton2</asp:LinkButton> <asp:CustomValidator ID="CustomValidator2" ValidationGroup="test2" runat="server" ClientValidationFunction="validateRequired" ErrorMessage="CustomValidator2" ControlToValidate="TextBox2" ValidateEmptyText="True"></asp:CustomValidator> 2. Place this script between head and body <script type="text/javascript" src="http://www.google.com/jsapi"></script> <script type="text/javascript"> google.load("jquery", "1.3.2");</script> <script type="text/javascript"> function validateRequired(oSrc, args) { var txt = $get(oSrc.controltovalidate); var pass = (args.Value.length > 0); if (pass) { $('#' + txt.id).removeClass('requirederror'); args.IsValid = true; } else { // set length css class to error. $('#' + txt.id).addClass('requirederror'); args.IsValid = false; } } </script> When you click on first link, only 1 validator execute, when you click on second link another textbox validate. It happened, because i separate them by ValidationGroup. It works as expected. Now add between header and body <script type="text/javascript" src="jquery.watermark.js"></script> And now when you click on any linkbutton validation happened for all controls. Which not suppose to be. Is any way to fix it. I dont use watermark library on my page, but its in Master page.Im using Nov 11 release. Thanks a lot for great product Nov 23, 2009 issue 10 (Watermak classname property is not working on Google Chrome) reported by K.Musaied - What steps will reproduce the problem? 1. add a class name to your code. 2. run the page on chrome. What is the expected output? What do you see instead? It should apply the class on the textbox but it does not on chrome. What version of the product are you using? On what operating system? v3.0.2 OS.Vista Please provide any additional information below. test your sample file on chrome What steps will reproduce the problem? 1. add a class name to your code. 2. run the page on chrome. What is the expected output? What do you see instead? It should apply the class on the textbox but it does not on chrome. What version of the product are you using? On what operating system? v3.0.2 OS.Vista Please provide any additional information below. test your sample file on chrome Nov 19, 2009 issue 9 (Form doesn't submit in Chrome when submitting programmatical...) reported by TheMit - What steps will reproduce the problem? 1. Use Chrome. 2. Attempt to submit a form programmatically upon a button click, like so: $('#searchSubmitLink').click(function() { $(this).closest('form').submit(); }); What is the expected output? What do you see instead? I expect the form to be submitted. While all of the watermarked form fields are cleared out, the form isn't submitted. If instead I submit using standard browser behavior (pressing Enter in an input), it clears watermarks and submits properly. What version of the product are you using? On what operating system? Using 3.0.2, with jQuery 1.3.2. Please provide any additional information below. The same code works fine in IE8 & FF3.5. Doesn't work in the latest Chrome. What steps will reproduce the problem? 1. Use Chrome. 2. Attempt to submit a form programmatically upon a button click, like so: $('#searchSubmitLink').click(function() { $(this).closest('form').submit(); }); What is the expected output? What do you see instead? I expect the form to be submitted. While all of the watermarked form fields are cleared out, the form isn't submitted. If instead I submit using standard browser behavior (pressing Enter in an input), it clears watermarks and submits properly. What version of the product are you using? On what operating system? Using 3.0.2, with jQuery 1.3.2. Please provide any additional information below. The same code works fine in IE8 & FF3.5. Doesn't work in the latest Chrome. Nov 11, 2009 r27 ([No log message]) committed by t...@speednet.biz - [No log message] [No log message] Nov 11, 2009 issue 8 (Error when there's no form on the page: this.form is null) Status changed by t...@speednet.biz - FIXED IN VERSION 3.0.2. Thank you for the feedback. Added a test to ensure there is a form on the page before attempting to override the form submit function. Status: Fixed FIXED IN VERSION 3.0.2. Thank you for the feedback. Added a test to ensure there is a form on the page before attempting to override the form submit function. Status: Fixed Nov 11, 2009 issue 7 (Resolving conflict with ASP.NET validators) Status changed by t...@speednet.biz - FIXED IN VERSION 3.0.2. Thank you for the feedback. Added capability to hijack any number of JavaScript functions that, when called, first hide all watermarks and then call the originally-intended function. Initially, only the Page_ClientValidate is specified to be overridden. Others will be added if feedback dictates. If a function specified is not found on the page, the function name is ignored on that page. Status: Fixed FIXED IN VERSION 3.0.2. Thank you for the feedback. Added capability to hijack any number of JavaScript functions that, when called, first hide all watermarks and then call the originally-intended function. Initially, only the Page_ClientValidate is specified to be overridden. Others will be added if feedback dictates. If a function specified is not found on the page, the function name is ignored on that page. Status: Fixed Nov 11, 2009 jquery.watermark-3.0.2.zip (Watermark plugin for jQuery v3.0.2 (current release)) file uploaded by t...@speednet.biz - Labels: Featured Type-Archive Labels: Featured Type-Archive Nov 11, 2009 r26 (Version 3.0.2 (2009-11-11) Solved Issue #7 (Resolving conf...) committed by t...@speednet.biz - Version 3.0.2 (2009-11-11) Solved Issue #7 (Resolving conflict with ASP.NET validators) - Added capability to hijack any number of JavaScript functions that, when called, first hide all watermarks and then call the originally- intended function. Initially, only the Page_ClientValidate is specified to be overridden. Others will be added if feedback dictates. If a function specified is not found on the page, the function name is ignored on that page. Solved Issue #8 (Error when there's no form on the page: this.form is null) - Added a test to ensure there is a form on the page before attempting to override the form submit function. The $.watermark.version property will properly return "3.0.2". The version number was not updated in the 3.0.1 release, and continued to report as 3.0. Added detection for the presence of watermark activity on a page so that hideAll() will not bother trying to do anything if there are no watermarks to hide. Also, calling hideAll() multiple times in succession will process the elements on the page only once. Switched from YUI Compressor to Microsoft Ajax Minifier for minification. The new Microsoft minifier produces more compact code than YUI, so even with the additional code, the overall size is not much bigger than the last release. (I have made a free online JavaScript compressor available with both Microsoft and YUI compression methods at http://www.lotterypost.com/js-compress.aspx.) Version 3.0.2 (2009-11-11) Solved Issue #7 (Resolving conflict with ASP.NET validators) - Added capability to hijack any number of JavaScript functions that, when called, first hide all watermarks and then call the originally- intended function. Initially, only the Page_ClientValidate is specified to be overridden. Others will be added if feedback dictates. If a function specified is not found on the page, the function name is ignored on that page. Solved Issue #8 (Error when there's no form on the page: this.form is null) - Added a test to ensure there is a form on the page before attempting to override the form submit function. The $.watermark.version property will properly return "3.0.2". The version number was not updated in the 3.0.1 release, and continued to report as 3.0. Added detection for the presence of watermark activity on a page so that hideAll() will not bother trying to do anything if there are no watermarks to hide. Also, calling hideAll() multiple times in succession will process the elements on the page only once. Switched from YUI Compressor to Microsoft Ajax Minifier for minification. The new Microsoft minifier produces more compact code than YUI, so even with the additional code, the overall size is not much bigger than the last release. (I have made a free online JavaScript compressor available with both Microsoft and YUI compression methods at http://www.lotterypost.com/js-compress.aspx.) Nov 11, 2009 issue 8 (Error when there's no form on the page: this.form is null) commented on by i.t.ignatov - In general I guess that it's invalid HTML. However in my case I'm not using it to submit data but only to filter the information on a page using JavaScript. After I put a form element everything worked fine. Still I think it will be better if it works even without form. As far as I remember in ASP.NET webforms it's possible to have only one form.. and in some cases someone may need to put a control that performs client-side-only tasks outside of this form. In conclusion I think that if this is not hard to fix and won't introduce any performance penalties maybe it's worth to be addressed. P.S. Great plugin btw! :-) In general I guess that it's invalid HTML. However in my case I'm not using it to submit data but only to filter the information on a page using JavaScript. After I put a form element everything worked fine. Still I think it will be better if it works even without form. As far as I remember in ASP.NET webforms it's possible to have only one form.. and in some cases someone may need to put a control that performs client-side-only tasks outside of this form. In conclusion I think that if this is not hard to fix and won't introduce any performance penalties maybe it's worth to be addressed. P.S. Great plugin btw! :-) Nov 11, 2009 issue 8 (Error when there's no form on the page: this.form is null) commented on by a.cyberdemon - I am experiencing the same issue whilst using asp.net webforms... which always has a form. I am experiencing the same issue whilst using asp.net webforms... which always has a form. Oct 16, 2009 issue 8 (Error when there's no form on the page: this.form is null) commented on by t...@speednet.biz - I'll check it out, but when would you ever have input or textarea controls without a form? Isn't that invalid HTML? I'll check it out, but when would you ever have input or textarea controls without a form? Isn't that invalid HTML? Oct 04, 2009 issue 8 (Error when there's no form on the page: this.form is null) reported by i.t.ignatov - What steps will reproduce the problem? 1. Create a simple HTML page with only one text input on it. 2. Add the following script $("#myTextbox").watermark("Enter your name"); 3. The following error appears: "this.form is null". What is the expected output? What do you see instead? I expect that the watermark should be added to the control. Instead I got the following: >> Error: this.form is null \| Source File: jquery.watermark.js \| Line: 422 What version of the product are you using? On what operating system? Product version: 3.0.1 Operating system: Windows XP Pro Browser: Firefox 3.5.3 Please provide any additional information below. What steps will reproduce the problem? 1. Create a simple HTML page with only one text input on it. 2. Add the following script $("#myTextbox").watermark("Enter your name"); 3. The following error appears: "this.form is null". What is the expected output? What do you see instead? I expect that the watermark should be added to the control. Instead I got the following: >> Error: this.form is null \| Source File: jquery.watermark.js \| Line: 422 What version of the product are you using? On what operating system? Product version: 3.0.1 Operating system: Windows XP Pro Browser: Firefox 3.5.3 Please provide any additional information below. Sep 27, 2009 issue 7 (Resolving conflict with ASP.NET validators) reported by herbcaudill - What steps will reproduce the problem? 1. On an ASP.NET form, add a regularexpressionvalidator to a textbox that has a watermark applied to it 2. Press submit; the validator will validate against the watermark text and fail. In order to get this working on my site, I've hijacked the Page_ClientValidate function as follows: // Allows you to hijack the Page_ClientValidate function and add // custom functionality before validation takes place. addTo_Page_ClientValidate = function(func) { if (typeof Page_ClientValidate != 'function') { Page_ClientValidate = func; } else { var oldPage_ClientValidate = Page_ClientValidate; Page_ClientValidate = function(validationGroup) { oldPage_ClientValidate(validationGroup); func(validationGroup); } } }; // Fix to make jQuery watermark play nice with ASP.NET postbacks addTo_Page_ClientValidate(function(validationGroup) { $.watermark.hideAll(); }); What steps will reproduce the problem? 1. On an ASP.NET form, add a regularexpressionvalidator to a textbox that has a watermark applied to it 2. Press submit; the validator will validate against the watermark text and fail. In order to get this working on my site, I've hijacked the Page_ClientValidate function as follows: // Allows you to hijack the Page_ClientValidate function and add // custom functionality before validation takes place. addTo_Page_ClientValidate = function(func) { if (typeof Page_ClientValidate != 'function') { Page_ClientValidate = func; } else { var oldPage_ClientValidate = Page_ClientValidate; Page_ClientValidate = function(validationGroup) { oldPage_ClientValidate(validationGroup); func(validationGroup); } } }; // Fix to make jQuery watermark play nice with ASP.NET postbacks addTo_Page_ClientValidate(function(validationGroup) { $.watermark.hideAll(); }); Sep 12, 2009 issue 6 (Can I keep the watermark till the first character is typed?) commented on by gerwin.b...@bizzons.com - Thanks for the detailed explanation... Good thoughts on usability. Thx! Thanks for the detailed explanation... Good thoughts on usability. Thx! Sep 11, 2009 issue 6 (Can I keep the watermark till the first character is typed?) Status changed by t...@speednet.biz - Status: WontFix Status: WontFix Sep 11, 2009 issue 5 (postback issue with ASP.NET DropDownList) Status changed by t...@speednet.biz - Fixed in version 3.0.1. Status: Fixed Fixed in version 3.0.1. Status: Fixed Sep 11, 2009 r25 (- Updated wiki with latest code and changelog.) committed by t...@speednet.biz - - Updated wiki with latest code and changelog. - Updated wiki with latest code and changelog. Sep 11, 2009 jquery.watermark-3.0.1.zip (Watermark plugin for jQuery v3.0.1 (current release)) file uploaded by t...@speednet.biz - Labels: Featured Type-Archive Labels: Featured Type-Archive Sep 11, 2009 r24 (Version 3.0.1 (2009-09-11) - Solved Issue #5 (postback iss...) committed by t...@speednet.biz - Version 3.0.1 (2009-09-11) - Solved Issue #5 (postback issue with ASP.NET DropDownList) - Fixed form submit bug with IE6 and IE7 that threw a JavaScript error when a form was submitted programmatically. - Minor cosmetic change suggested on jQuery issues list (Text blink when setting specific class). Reversed two lines so that class name is set before the watermark text is set. Version 3.0.1 (2009-09-11) - Solved Issue #5 (postback issue with ASP.NET DropDownList) - Fixed form submit bug with IE6 and IE7 that threw a JavaScript error when a form was submitted programmatically. - Minor cosmetic change suggested on jQuery issues list (Text blink when setting specific class). Reversed two lines so that class name is set before the watermark text is set. Sep 11, 2009 issue 5 (postback issue with ASP.NET DropDownList) Status changed by t...@speednet.biz - Thank you for the demo page of the bug. I have confirmed that it is a bug in IE6 and IE7, and I have worked up a solution that I will deploy shortly. The bug occurs because IE6 and IE7 do not use a standard Function prototype on the submit() function, but instead use a natively bound (proprietary) function call. The solution I worked up seems to operate correctly, but I strongly recommend testing all your various scenarios after installing the new solution, because I have to assume that IE will pass all the arguments correctly. It SAYS it will do it, but hey, it's IE, so "trust but verify" is the best approach. The solution will be posted as version 3.0.1. Status: Accepted Thank you for the demo page of the bug. I have confirmed that it is a bug in IE6 and IE7, and I have worked up a solution that I will deploy shortly. The bug occurs because IE6 and IE7 do not use a standard Function prototype on the submit() function, but instead use a natively bound (proprietary) function call. The solution I worked up seems to operate correctly, but I strongly recommend testing all your various scenarios after installing the new solution, because I have to assume that IE will pass all the arguments correctly. It SAYS it will do it, but hey, it's IE, so "trust but verify" is the best approach. The solution will be posted as version 3.0.1. Status: Accepted Sep 11, 2009 issue 6 (Can I keep the watermark till the first character is typed?) commented on by t...@speednet.biz - For many reasons, no. Primarily, that's not the way watermarks work across the Web. Just try adding a comment to this issue, and you will see the Google watermark functionality act just like the plugin does. It would add a layer of confusion for many users, as they would try deleting characters that seemingly have been mistakenly left in the input space. Further, it would add additional complexity to the code, bringing it further and further from a light-weight solution. Finally, a watermark is the wrong solution for what you want. The functionality you describe is already available, and is a convention of the Windows operating system. When you tab into a field, the browser (or Windows) highlights all the text in the space, and upon the first keystroke it is replaced. If you're going to have an input space that leaves text in the entry space until a key is pressed, that is the proper way to do it. You can do that by calling the .select() function on the element in the focus event. For many reasons, no. Primarily, that's not the way watermarks work across the Web. Just try adding a comment to this issue, and you will see the Google watermark functionality act just like the plugin does. It would add a layer of confusion for many users, as they would try deleting characters that seemingly have been mistakenly left in the input space. Further, it would add additional complexity to the code, bringing it further and further from a light-weight solution. Finally, a watermark is the wrong solution for what you want. The functionality you describe is already available, and is a convention of the Windows operating system. When you tab into a field, the browser (or Windows) highlights all the text in the space, and upon the first keystroke it is replaced. If you're going to have an input space that leaves text in the entry space until a key is pressed, that is the proper way to do it. You can do that by calling the .select() function on the element in the focus event. Sep 11, 2009 issue 6 (Can I keep the watermark till the first character is typed?) reported by gerwin.brunner - Right now, when a field gets the focus the watermark gets cleared. Would it be possible to keep the watermark after getting the focus till the user types in the first letter? That would really be cool. Right now, when a field gets the focus the watermark gets cleared. Would it be possible to keep the watermark after getting the focus till the user types in the first letter? That would really be cool. Sep 11, 2009 issue 5 (postback issue with ASP.NET DropDownList) reported by fbi1970 - What steps will reproduce the problem? 1. Place a DropDownList with AutoPostBack="True" 2. Place any TextBoxes with at least one watermark 3. Load IE6 or IE7 3. Change selected item in DropDownList causes javascript error What is the expected output? What do you see instead? No javascript errors What version of the product are you using? On what operating system? Windows 2008 or 7 + IIS 7.0 or 7.5 + .NET 3.5SP1 + IE6 or 7 IE8 and Firefox do not show any errors. Please provide any additional information below. Error shown is: "Object doesn't support this property or method". The line where the error is found is (at bottom of code): $form.data(dataFormSubmit).apply($form[0], arguments); Attached is a simple test page. Kind Regards What steps will reproduce the problem? 1. Place a DropDownList with AutoPostBack="True" 2. Place any TextBoxes with at least one watermark 3. Load IE6 or IE7 3. Change selected item in DropDownList causes javascript error What is the expected output? What do you see instead? No javascript errors What version of the product are you using? On what operating system? Windows 2008 or 7 + IIS 7.0 or 7.5 + .NET 3.5SP1 + IE6 or 7 IE8 and Firefox do not show any errors. Please provide any additional information below. Error shown is: "Object doesn't support this property or method". The line where the error is found is (at bottom of code): $form.data(dataFormSubmit).apply($form[0], arguments); Attached is a simple test page. Kind Regards Sep 10, 2009 issue 4 (Dragging and dropping text does not replace the watermark) Status changed by t...@speednet.biz - Fixed in v 3.0. Status: Fixed Fixed in v 3.0. Status: Fixed Sep 10, 2009 issue 1 (Integrate with Safari input type="search") Status changed by t...@speednet.biz - Fixed in v 3.0. Status: Fixed Fixed in v 3.0. Status: Fixed Sep 10, 2009 r23 (- Checking in v3.0 components ) committed by t...@speednet.biz - - Checking in v3.0 components - Checking in v3.0 components Sep 10, 2009 jquery.watermark-3.0.zip (Watermark plugin for jQuery v3.0 (current release)) file uploaded by t...@speednet.biz - Labels: Featured Type-Archive Labels: Featured Type-Archive Sep 10, 2009 r22 (- Added zip file download package for version 3.0 - Changed...) committed by t...@speednet.biz - - Added zip file download package for version 3.0 - Changed naming convention of files, removing the version number from the file name and folder name. In real-world usage, it can be disruptive to try to implement a new version of the plugin if the file name includes the version number. There are some who feel differently about this issue, and prefer the version number in the file name, but I prefer it removed. It is easy to add back into the file name, if desired by the individual developer. - Added zip file download package for version 3.0 - Changed naming convention of files, removing the version number from the file name and folder name. In real-world usage, it can be disruptive to try to implement a new version of the plugin if the file name includes the version number. There are some who feel differently about this issue, and prefer the version number in the file name, but I prefer it removed. It is easy to add back into the file name, if desired by the individual developer. Sep 10, 2009 r21 (Source code changes for version 3.0 - Solved Issue #1 - Int...) committed by t...@speednet.biz - Source code changes for version 3.0 - Solved Issue #1 - Integrate with WebKit browsers that support input tags with type="search". (Issue list refers to Safari alone, but it turns out that Google Chrome also supports type="search" elements.) - Solved Issue #4 - Dragging and dropping text now replaces the watermark. This was the most significant change, and required several work-arounds due to a variety of browser glitches. - Added support for native browser watermarks in WebKit browsers ("placeholder" attribute). New "useNative" option in the plugin allows native browser watermark support to be enabled/disabled globally, or for individual watermarks. When a watermark is created, the plugin detects if native browser support is available, and automatically uses it, as long as useNative is true. Two good reasons to turn off native support is the lack of CSS class name support (native watermark/placeholder is always light gray), and native watermarks/placeholders in type="search" elements do not always work properly with drag-and-drop. (Using the watermark plugin support (useNative:false) for type="search" elements does work properly with drag-and-drop.) However, for typical non-styled watermark usage, native browser support is encouraged, by leaving useNative set to true. (Default is true). - New "$.watermark.options" object stores the default options for watermarks. There are currently two properties of $.watermark.options: className and useNative. (BREAKING CHANGE: $.watermark.className has been eliminated, and replaced with $.watermark.options.className.) The use of an object to store default options is is keeping with current jQuery techniques, and allows for future expansion in a much more flexible manner. - New watermark calling signature - $( <selector> ).watermark( [text] , [options] ); - Example: $("#myElement").watermark("Enter Username", {className: "inputspace", useNative: false}); - Plugin continues to support the use of a string value for the second argument, for backward compatibility. If a string value is passed for the second argument, it is used as the className for the watermark, overriding the default value in $.watermark.options.className. - "useNative" option can be either a boolean or a function. If useNative is a function, then the function is evaluated for each element in the matched set, returning a boolean value specifying if native support is enabled for the element. The function is passed one argument -- a jQuery object containing the element being tested as the only element in its matched set -- and the DOM element being tested is the object on which the function is invoked (the value of "this"). - Worked around jQuery/Chrome bug that would execute $(...).filter(...).each( fn ) twice for each element in the matched set. (Fairly confident this is a jQuery bug of some type.) - Fixed Chrome bug where password watermarks longer than 10 characters would cause the functionality to fail. - Added $.watermark.version (string value). Currently set to "3.0". - KNOWN ISSUES: 1. Opera support for drag-and-drop is terrible, even with version 10. It basically supports it when it feels like it. 2. WebKit native support for watermarks in Search elements (type="search") is poor with drag- and-drop. Sometimes it works, but it almost never supports dragging between Search elements. The demo page can be used to try it out and compare the functionality to the plugin's functionality. With Search elements, you should probably set useNative to false. 3. WebKit native support does not yet extend to textarea elements. (Limitation of WebKit browsers.) Source code changes for version 3.0 - Solved Issue #1 - Integrate with WebKit browsers that support input tags with type="search". (Issue list refers to Safari alone, but it turns out that Google Chrome also supports type="search" elements.) - Solved Issue #4 - Dragging and dropping text now replaces the watermark. This was the most significant change, and required several work-arounds due to a variety of browser glitches. - Added support for native browser watermarks in WebKit browsers ("placeholder" attribute). New "useNative" option in the plugin allows native browser watermark support to be enabled/disabled globally, or for individual watermarks. When a watermark is created, the plugin detects if native browser support is available, and automatically uses it, as long as useNative is true. Two good reasons to turn off native support is the lack of CSS class name support (native watermark/placeholder is always light gray), and native watermarks/placeholders in type="search" elements do not always work properly with drag-and-drop. (Using the watermark plugin support (useNative:false) for type="search" elements does work properly with drag-and-drop.) However, for typical non-styled watermark usage, native browser support is encouraged, by leaving useNative set to true. (Default is true). - New "$.watermark.options" object stores the default options for watermarks. There are currently two properties of $.watermark.options: className and useNative. (BREAKING CHANGE: $.watermark.className has been eliminated, and replaced with $.watermark.options.className.) The use of an object to store default options is is keeping with current jQuery techniques, and allows for future expansion in a much more flexible manner. - New watermark calling signature - $( <selector> ).watermark( [text] , [options] ); - Example: $("#myElement").watermark("Enter Username", {className: "inputspace", useNative: false}); - Plugin continues to support the use of a string value for the second argument, for backward compatibility. If a string value is passed for the second argument, it is used as the className for the watermark, overriding the default value in $.watermark.options.className. - "useNative" option can be either a boolean or a function. If useNative is a function, then the function is evaluated for each element in the matched set, returning a boolean value specifying if native support is enabled for the element. The function is passed one argument -- a jQuery object containing the element being tested as the only element in its matched set -- and the DOM element being tested is the object on which the function is invoked (the value of "this"). - Worked around jQuery/Chrome bug that would execute $(...).filter(...).each( fn ) twice for each element in the matched set. (Fairly confident this is a jQuery bug of some type.) - Fixed Chrome bug where password watermarks longer than 10 characters would cause the functionality to fail. - Added $.watermark.version (string value). Currently set to "3.0". - KNOWN ISSUES: 1. Opera support for drag-and-drop is terrible, even with version 10. It basically supports it when it feels like it. 2. WebKit native support for watermarks in Search elements (type="search") is poor with drag- and-drop. Sometimes it works, but it almost never supports dragging between Search elements. The demo page can be used to try it out and compare the functionality to the plugin's functionality. With Search elements, you should probably set useNative to false. 3. WebKit native support does not yet extend to textarea elements. (Limitation of WebKit browsers.) Sep 07, 2009 issue 2 (Postback in ASP.NET using linkbutton failes) commented on by joakim.fischer - Ok. Do so. The error I got was easily produced but if you don't get the same I'm sure there is some other issue as you say... did not have the time to set up a demo site I'm afraid and I'm fine with using buttons instead of link buttons at the moment. Ok. Do so. The error I got was easily produced but if you don't get the same I'm sure there is some other issue as you say... did not have the time to set up a demo site I'm afraid and I'm fine with using buttons instead of link buttons at the moment. Sep 07, 2009 issue 2 (Postback in ASP.NET using linkbutton failes) Status changed by t...@speednet.biz - I'm going to close the issue as non-reproduceable. Please feel free to start a new issue if you are able to produce a demo of the issue in question. (Or if any other issue comes up.) Status: Invalid I'm going to close the issue as non-reproduceable. Please feel free to start a new issue if you are able to produce a demo of the issue in question. (Or if any other issue comes up.) Status: Invalid Sep 07, 2009 issue 3 (Windows 7 IE8 Error) Status changed by t...@speednet.biz - Status: Invalid Status: Invalid Aug 25, 2009 issue 2 (Postback in ASP.NET using linkbutton failes) commented on by joakim.fischer - I'm using jquery 1.3.2. I dont have an example site I'm afraid. I changed all links to input-submit now and its working good. I will try to test it again soon. I'm using jquery 1.3.2. I dont have an example site I'm afraid. I changed all links to input-submit now and its working good. I will try to test it again soon.

r21 (Source code changes for version 3.0 - Solved Issue #1 - Int...) committed by t...@speednet.biz - Source code changes for version 3.0 - Solved Issue #1 - Integrate with WebKit browsers that support input tags with type="search". (Issue list refers to Safari alone, but it turns out that Google Chrome also supports type="search" elements.) - Solved Issue #4 - Dragging and dropping text now replaces the watermark. This was the most significant change, and required several work-arounds due to a variety of browser glitches. - Added support for native browser watermarks in WebKit browsers ("placeholder" attribute). New "useNative" option in the plugin allows native browser watermark support to be enabled/disabled globally, or for individual watermarks. When a watermark is created, the plugin detects if native browser support is available, and automatically uses it, as long as useNative is true. Two good reasons to turn *off* native support is the lack of CSS class name support (native watermark/placeholder is always light gray), and native watermarks/placeholders in type="search" elements do not always work properly with drag-and-drop. (Using the watermark plugin support (useNative:false) for type="search" elements *does* work properly with drag-and-drop.) However, for typical non-styled watermark usage, native browser support is encouraged, by leaving useNative set to true. (Default is true). - New "$.watermark.options" object stores the default options for watermarks. There are currently two properties of $.watermark.options: className and useNative. (BREAKING CHANGE: $.watermark.className has been eliminated, and replaced with $.watermark.options.className.) The use of an object to store default options is is keeping with current jQuery techniques, and allows for future expansion in a much more flexible manner. - New watermark calling signature - $( <selector> ).watermark( [text] , [options] ); - Example: $("#myElement").watermark("Enter Username", {className: "inputspace", useNative: false}); - Plugin continues to support the use of a string value for the second argument, for backward compatibility. If a string value is passed for the second argument, it is used as the className for the watermark, overriding the default value in $.watermark.options.className. - "useNative" option can be either a boolean or a function. If useNative is a function, then the function is evaluated for each element in the matched set, returning a boolean value specifying if native support is enabled for the element. The function is passed one argument -- a jQuery object containing the element being tested as the only element in its matched set -- and the DOM element being tested is the object on which the function is invoked (the value of "this"). - Worked around jQuery/Chrome bug that would execute $(...).filter(...).each( fn ) twice for each element in the matched set. (Fairly confident this is a jQuery bug of some type.) - Fixed Chrome bug where password watermarks longer than 10 characters would cause the functionality to fail. - Added $.watermark.version (string value). Currently set to "3.0". - KNOWN ISSUES: 1. Opera support for drag-and-drop is terrible, even with version 10. It basically supports it when it feels like it. 2. WebKit native support for watermarks in Search elements (type="search") is poor with drag- and-drop. Sometimes it works, but it almost never supports dragging between Search elements. The demo page can be used to try it out and compare the functionality to the plugin's functionality. With Search elements, you should probably set useNative to false. 3. WebKit native support does not yet extend to textarea elements. (Limitation of WebKit browsers.)

Source code changes for version 3.0 - Solved Issue #1 - Integrate with WebKit browsers that support input tags with type="search". (Issue list refers to Safari alone, but it turns out that Google Chrome also supports type="search" elements.) - Solved Issue #4 - Dragging and dropping text now replaces the watermark. This was the most significant change, and required several work-arounds due to a variety of browser glitches. - Added support for native browser watermarks in WebKit browsers ("placeholder" attribute). New "useNative" option in the plugin allows native browser watermark support to be enabled/disabled globally, or for individual watermarks. When a watermark is created, the plugin detects if native browser support is available, and automatically uses it, as long as useNative is true. Two good reasons to turn *off* native support is the lack of CSS class name support (native watermark/placeholder is always light gray), and native watermarks/placeholders in type="search" elements do not always work properly with drag-and-drop. (Using the watermark plugin support (useNative:false) for type="search" elements *does* work properly with drag-and-drop.) However, for typical non-styled watermark usage, native browser support is encouraged, by leaving useNative set to true. (Default is true). - New "$.watermark.options" object stores the default options for watermarks. There are currently two properties of $.watermark.options: className and useNative. (BREAKING CHANGE: $.watermark.className has been eliminated, and replaced with $.watermark.options.className.) The use of an object to store default options is is keeping with current jQuery techniques, and allows for future expansion in a much more flexible manner. - New watermark calling signature - $( <selector> ).watermark( [text] , [options] ); - Example: $("#myElement").watermark("Enter Username", {className: "inputspace", useNative: false}); - Plugin continues to support the use of a string value for the second argument, for backward compatibility. If a string value is passed for the second argument, it is used as the className for the watermark, overriding the default value in $.watermark.options.className. - "useNative" option can be either a boolean or a function. If useNative is a function, then the function is evaluated for each element in the matched set, returning a boolean value specifying if native support is enabled for the element. The function is passed one argument -- a jQuery object containing the element being tested as the only element in its matched set -- and the DOM element being tested is the object on which the function is invoked (the value of "this"). - Worked around jQuery/Chrome bug that would execute $(...).filter(...).each( fn ) twice for each element in the matched set. (Fairly confident this is a jQuery bug of some type.) - Fixed Chrome bug where password watermarks longer than 10 characters would cause the functionality to fail. - Added $.watermark.version (string value). Currently set to "3.0". - KNOWN ISSUES: 1. Opera support for drag-and-drop is terrible, even with version 10. It basically supports it when it feels like it. 2. WebKit native support for watermarks in Search elements (type="search") is poor with drag- and-drop. Sometimes it works, but it almost never supports dragging between Search elements. The demo page can be used to try it out and compare the functionality to the plugin's functionality. With Search elements, you should probably set useNative to false. 3. WebKit native support does not yet extend to textarea elements. (Limitation of WebKit browsers.)

Last 7 days

Last 30 days

Earlier this year