You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To see the bug, put this in a directory index file, and click on SUBMIT while the placeholder is displayed (submits form to same file with get parameters "?txt1="). This example automatically navigates "back" after the form submit, and the bug is seen.
You can also see this bug by removing the "window.history.back();" line and manually using the browser's back button.
The text was updated successfully, but these errors were encountered:
sbull
added a commit
to sbull/jquery-placeholder
that referenced
this issue
Feb 24, 2012
Lacking an acceptable solution for this in the actual placeholder code itself (see the comments in Pull Request #59), a trick like the following can be used as a workaround:
Mathias, I'm wondering if you think it might be appropriate to add this as an option to the placeholder code? Either as a config option (similar to how a custom class name might be treated, $.fn.placeholder.removeIdenticalValues) or as an option/parameter to the .placeholder() call? Or if you think it might be desirable to run something like this by default during the .placeholder() call?
There are certain navigation scenarios that can cause placeholder to fail. The following is an example.
To see the bug, put this in a directory index file, and click on SUBMIT while the placeholder is displayed (submits form to same file with get parameters "?txt1="). This example automatically navigates "back" after the form submit, and the bug is seen.
You can also see this bug by removing the "window.history.back();" line and manually using the browser's back button.
The text was updated successfully, but these errors were encountered: