This Week in jQuery, vol. 1

13 thoughts on “This Week in jQuery, vol. 1”

1. Pingback: This Week in jQuery UI vol. 1 « jQuery UI Blog

2. dafire on March 13, 2009 at 8:30 am said:

   about the jslint quick tip… if you use komodo for editing your js files it does error checking in the background all the time.
3. Jason Kuhn on March 13, 2009 at 9:33 am said:

   An addition to the quick tip:

   If you’re writing singleton objects (typically options in jquery/ui), and you have a value that you might change frequently, such as setting the active tab temporarily, it’s a good idea to ensure that value isn’t the last in the list.

   var options = {
   selected: 2,
   orientation: ‘vertical’
   };

   this way you can easily comment it out without having the extra comma issue addressed in the quick tip above.

   this example will cause errors in some browsers:
   var options = {
   orientation: ‘vertical’,
   //selected: 2
   };

   do this instead:
   var options = {
   //selected: 2,
   orientation: ‘vertical’
   };
4. Kevin Peno on March 13, 2009 at 11:59 am said:

   RE the IE compatability problems. Another thing developers should do is turn on strict javascript warnings in browsers, such as firefox, during development. This will flag other issues that may also cause problems with compatability (including trailing commas last I checked), mostly in relation to syntax. That way when you test in IE, if it is not your primary development browser, you are less likely to run in to problems.

   I like the idea of this blog. I look forward to some cool tips and exposure of less popular, yet useful, plugins!
5. Nikola on March 13, 2009 at 1:05 pm said:

   I look forward to reading these every week.
6. Mack Hankins on March 13, 2009 at 1:34 pm said:

   I have enjoyed reading the new book. Now on chapter 5 and I have never used Jquery before. I will really enjoy this part of your blog.
7. Gordon on March 13, 2009 at 3:08 pm said:

   Trailing comma in php is a best practice? I never got that memo.
8. Karl Swedberg on March 13, 2009 at 4:25 pm said:

   @Gordon: yeah, I initially had written, “considered by some to be a best practice,” but I was afraid I was getting too wordy. Anyway, at least Drupal’s coding standards document recommends it: “Note the comma at the end of the last array element; This is not a typo! It helps prevent parsing errors if another element is placed at the end of the list later.” In retrospect, I probably should have gone with the much weaker statement that the trailing comma is “perfectly valid syntax,” as noted in the PHP Manual.
9. Bramus! on March 14, 2009 at 6:23 am said:

   Think that a typo slipped into this post: “Introduction to ExtJS” ;-)
10. Matt S. on March 16, 2009 at 10:23 am said:

    I previously forced my users to switch to Firefox for the web app I’ve built if only for the speed increase (lots and lots of Ajax loads to recreate a Java program). A couple of runs through Jslint found the one errant comma and IE works now too.

    Then again, I almost want to the put the comma back to continue to force Firefox in hopes they will like it and get it at home too.
11. Ivan on March 16, 2009 at 1:58 pm said:

    shouldn’t that ‘bar’:’rafaeli’, ? ;)
12. Howard Jess on March 19, 2009 at 6:40 pm said:

    An alternate syntax for object literals that can help avoid the trailing comma problem is nice (if you can get used to it):

    var foo = {
    bar: ‘ice cream’
    ,baz: ‘luhrmann’
    ,bongo: ‘feinman’
    }
13. moby_dick on March 25, 2009 at 3:37 am said:

    You can also use the following regex to find the wrong commas:

    ,[\s\r\n]*[\}\]]