Skip to main content

jQuery quirks

Ok folks. let's get technical here (been a while, hasn't it)?

So I decided to start using jQuery instead of Prototype as the JavaScript framework for my next project. Overall I am very happy with it (great plugins, good performance, cleaner overall structure, etc...).

It does have a few weird things about it though which people should bear in mind. Nothing that would stop people from using it, but things people should know.

In Prototype, the $() function returns an HTML element and the Prototype uses the prototype keyword to add extra functionality to the vanilla elements in the page (hence its name).

In jQuery, the $() function actually returns a jQuery object which is bound to the HTML element. This jQuery object then encompasses most of the functionality you will ever need on an element.

For the most part, this is a good thing. By using this strategy, jQuery is non invasive
and will play nice with any other JS framework (it even has a noConflict mode in case you want to use it with Prototype which will assign the $() function to any other combo you want).

However, when you use the $() function in jQuery, then you have to be aware that you are not really calling an HTML element so the standard HTML attributes may not be there.

Here is an example.

Let's say you have a text field


<input name="myTextField" id="myTextField" value="Hello Earth" type="text">

Without jQuery you would have to do this


var myTextField = document.getElementById('myTextField')


In jQuery you can simply use the $() function instead.

var myTextField = $('#myTextField');

However, let's say you need to update its value. You would think this would be the way to do it:

myTextField.value = "Hello Mars";

For some reason though, you find it is not working and this is driving you nuts. Why is this the case?

The reason is that myTextField is actually a jQuery object, not an HTML element. So the way to update a jQuery object's value is by using the val function.

myTextField.val("Hello Mars");

Once you remember that, then you should be plain sailing.

The only thing is that sometimes you may need to call an obscure HTML element attribute like scrollBy. There are plugins to deal with it, but nothing native in jQuery. Currently I am falling back to document.getElementById to get these. This is not necessarily a bad thing because jQuery, as I said before, is non invasive so it leaves the rest of your JS alone (as a good framework should).

UPDATE

I just found out you can use jQuery's get() function in order to access the actual HTML element(s) instead of using document.getElementById. In other words, the following should work:

myTextField.get()[0].value = "Hello Mars";

Note the [0] is needed because get returns an array of elements.

Comments

Anonymous said…
Or
myTextField[0].value = "Hello Mars";

Popular posts from this blog

Master of my domain

Hi All, I just got myself a new domain ( http://www.skuunk.com ). The reason is that Blogspot.com is offering cheap domain via GoDaddy.com and I thought after having this nickname for nigh on 10 years it was time to buy the domain before someone else did (also I read somewhere that using blogspot.com in your domain is the equivalent of an aol.com or hotmail.com email address...shudder...). Of course I forgot that I would have to re-register my blog everywhere (which is taking ages) not to mention set up all my stats stuff again. *sigh*. It's a blogger's life... In any case, don't forget to bookmark the new address and to vote me up on Technorati !

Elixir - destructuring, function overloading and pattern matching

Why am I covering 3 Elixir topics at once? Well, perhaps it is to show you how the three are used together. Individually, any of these 3 are interesting, but combined, they provide you with a means of essentially getting rid of conditionals and spaghetti logic. Consider the following function. def greet_beatle(person) do case person.first_name do "John" -> "Hello John." "Paul" -> "Good day Paul." "George" -> "Georgie boy, how you doing?" "Ringo" -> "What a drummer!" _-> "You are not a Beatle, #{person.first_name}" end end Yeah, it basically works, but there is a big old case statement in there. If you wanted to do something more as well depending on the person, you could easily end up with some spaghetti logic. Let's see how we can simplify this a little. def greet_beatle(%{first_name: first_name}) do case first_name d

Speeding up RSpec

So today I have been looking into getting our enormous battery of tests to run faster. I have yet to find anything that works for Cucumber, but I did find an interesting way to speed up RSpec which is detailed here. https://makandracards.com/makandra/950-speed-up-rspec-by-deferring-garbage-collection Basically, it seems that by not collecting garbage too frequently, you can make your tests run much faster (at the expense of memory management of course). We observed a 30% reduction in the time it takes to run an RSpec test suite. I did try to implement this on Cucumber, however because we need to store much more in memory to set up and tear down our objects, it meant that I kept running out of memory when I wasn't using the default Garbage Collection and the tests took even longer (so, buyer beware). I suppose if you had a small set of features though you might see some benefit.