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 !

Responsive Web Design

I wanted to go over Responsive Web Design using CSS. In the old days of web development, we had to code to common screen sizes (i.e. 800 X 600, 1024 X 768) and we patiently waited for people to upgrade their computers to have a decent amount of screen real estate so we could design things the way we really wanted. We also took on semi stretchy web layouts etc to expand and contract appropriately. Then about 2 or 3 years ago, Apple released this little device called an iPhone with a 320 X 480 resolution which took the world by storm and suddenly a lot of people were viewing your website on a tiny screen again... Anyways, as it can be difficult to design a site which looks good on 320 X 480 AND 1680 X 1050, we need to come up with some kind of solution. One way is to sniff the client and then use an appropriate stylesheet, but then you are mixing CSS with either JavaScript or server side programming and also potentially maintaining a list of appropriate clients and stylesheets. Also, you

jQuery: When does a library become a language?

jQuery is a great JavaScript library which allows web developers to write cross platform code, but some of its syntax looks like it is based more on Ruby than JavaScript. When does a library become a language? So first of all, what is the difference betwen a programming library and a programming language? A programming language is a means by which we (as humans) can give instructions to a computer to get it to do various tasks (algorithms, computations, etc...). They are largely artificial constructs created for human readability which then need to be compiled or interpreted into actual instructions which the computer can then carry out. A compiler turns a program into machine readable instructions ahead of time (compile time) where as an interpreter does so on the fly (runtime). Languages such as C and Java are generally compiled and JavaScript, Perl and Ruby are generally interpreted. While there is no real reason why this has to be the case, these factors normally affect the syntax