Demo: Using jQuery and perserving UI state

This week I had an interesting (email) conversation with a reader. Jason is a .Net developer using jQuery to build a simple form. On his page he had a UI feature where one of two DIVs were displayed. He had no problem with handling the logic of showing one div or another on the client side, but he was interested in how he could persist that change when he submitted his form. I worked up a simple demo of one way that this could be handled. I began by creating a very simple form.

<form id="myform" method="post"> name: <input type="text" name="name"><br/> email: <input type="text" name="email"><br/> <input type="submit">

</form> </code>

Instead of using two divs, I went with div that could be hidden or shown. The idea is that the div could be used for instructions.

<input type="button" id="toggleinstructions" value="Toggle Instructions"> <div id="instructions" style="display:none">These are the instructions for the slow people.</div>

Next I whipped up some quick jQuery to support the toggle:

$("#toggleinstructions").click(function() { $("#instructions").toggle() })

So far so good. How can we help persist the state of the instructions? Well one way would be with cookies. We could modify the click event handler to set a cookie every time the status changed. My problem with this though is that it seems a bit overkill to use a cookie just to remember the status of a UI item on the form. I decided to take another approach. What if we passed the status of the div when the form is submitted?

The first thing I did was to add a new hidden form field to the form:

<input type="hidden" name="instruction_status" id="instruction_status">

I then added a form submit handler:

$("#myform").submit(function() { status = $("#instructions").is(":visible") $("#instruction_status").val(status) })

This was my first time making use of the jQuery IS operator. This was a new one for me. As you can guess, it allows you to run a simple check on the currently selected item. In this case I’m checking for the visible property. This will return a boolean that then gets passed to the hidden form field.

Here is the complete template. You can see that I’ve added some server side logic to check for the hidden field and set the visibility accordingly.

<html> <head> <script type="text/javascript" src=""></script> <script> $(document).ready(function() { $("#toggleinstructions").click(function() { $("#instructions").toggle() })

$("#myform").submit(function() {
	status = $("#instructions").is(":visible")
}) }) &lt;/script&gt; &lt;/head&gt;


<cfparam name=”form.instruction_status” default=”false”> <input type=”button” id=”toggleinstructions” value=”Toggle Instructions”> <div id=”instructions” <cfif form.instruction_status is false>style=”display:none”</cfif>>These are the instructions for the slow people.</div>

<form id=”myform” method=”post”> <input type=”hidden” name=”instruction_status” id=”instruction_status”> name: <input type=”text” name=”name”><br/> email: <input type=”text” name=”email”><br/> <input type=”submit”>


</body> </html>

<cfdump var=”#form#”> </code>

Does it make sense for me to use a hidden form field for this? I don’t know. It kind of feels like I’m cluttering up the form with non-essential data. Then again, I do think I prefer this over the cookie approach. Either way - it’s just one more way to solve a problem in jQuery!

Raymond Camden's Picture

About Raymond Camden

Raymond is a developer advocate for Extend by Auth0. He focuses on serverless and enterprise cat demos. If you like this article, please consider visiting my Amazon Wishlist or donating via PayPal to show your support.

Lafayette, LA