Drupal 6 JavaScript and jQuery - Ebook-Cours.com

Integrating and Extending
Let's take a look at the beginning of this function:
$('input[name="search_block_form"]:not(.form-autocomplete)')
.each(function () {
// More code here...
}).addClass('form-autocomplete');
This first jQuery object grabs elements that match the query input[name="
search_block_form"]:not(.form-autocomplete). This is a little longer
than our usual query, but it is not difficult to understand.
The query is composed of three parts: an element query (input), an attribute
query ([name="search_block_form"]), and a negation pseudo-class (:not(.
form-autocomplete)). In short, the query looks for all elements with
an attribute name that has the value search_block_form. But due to the negation
pseudo-class, only elements that don't have the class form-autocomplete match.
The search_block_form name is used by the search module when it
creates a block containing a search text field. This part of the script could
be extended to find other text fields and turn them into autocompletion
fields. For example, to enable autocompletion in your theme's search box,
you would use the name search_theme_form.
In short, it matches all search text boxes that don't already have an autocomplete
feature. This query should match any Drupal search block, which typically looks
something like this:
As we can see from the previous code, it iterates through each of the matching
elements. In a moment, we will look at what happens to each element as it is iterated
over. Then, once that is done, the class form-autocomplete is added to each of the
matching elements.
[ 296 ]
This material is copyright and is licensed for the sole use by Richard Ostheimer on 18th June 2009
2205 hilda ave., , missoula, , 59801