Comments for Code Nomad

Comment on Announcing jQuery.Firebug by Grow Weed Indoors

Grow Weed Indoors — Mon, 26 Jul 2010 02:14:10 +0000

One of the best bloggers by far man. This article is well thought out and I totally agree with you on everything. Keep up the very good work!

Comment on Google Analytics Tagging with HTML5 data-* Attributes by Adam Boarman's dot com » Blog Archive » HTML5 Custom Data Attributes (data-*)

Thu, 24 Jun 2010 08:10:47 +0000

[...] To store custom web analytics tagging data as demonstrated by Jason Karns [...]

Comment on Cross Browser Inline-Block by jasonkarns

Tue, 25 May 2010 15:09:20 +0000

@chris I agree completely. The semantic value of my example markup is suspect. If headings and paragraphs are indeed all that’s contained in each ib-block item, then wrapping divs should be used (or HTML5 elements article/section) instead of ul/li. I began my example planning on using a list of products (title, description, image, price, rating, etc) and then stripped out all the extra content for brevity. At that point I forgot to revert the markup to divs.

Comment on Cross Browser Inline-Block by Chris Poteet

Chris Poteet — Mon, 24 May 2010 21:34:59 +0000

Interesting choice to use a list to structure content that contains paragraphs and headers. I would’ve gravitated to just the DIV. I wonder if the semantic value of the content you have above is a list of items?

PS. Subscribed to blog.

Comment on Roy.G.Biv alpha by Oliver Jones

Oliver Jones — Wed, 28 Apr 2010 18:25:07 +0000

Internet Explorer 8 is very good because it is as stable as Opera. I hate the previous versions of IE like IE6 because it hangs frequently. |

Comment on Announcing jQuery.Firebug by Todd

Todd — Tue, 13 Apr 2010 04:08:20 +0000

Hey Jason–

I just grabbed the plugin from SVN. Cool stuff, but I had a problem. Your line 338 is the following:

window.console["_" + method]($.makeArray(arguments).join(” “));

This is concatenating all objects as strings, which results in a much less useful output in Firebug (e.g. no drilling on object properties). Furthermore, it nerfs all the standard Firebug output in the same way, since you’re redefining the console.* functions to do the same.

Instead, I changed it to the following and had good results:

window.console["_" + method].apply(this,arguments);

After this, Firebug works as expected. Thanks!

Comment on CSS Reset by Tuukka Mustonen

Tuukka Mustonen — Wed, 17 Mar 2010 08:20:25 +0000

Hi, I can confirm your workaround. Removing font-size really did the trick and the annoying inheritance bloat vanished from Firebug.

Thanks for the tip!

Comment on JavaScript Best Practices by matt.acton

Wed, 03 Mar 2010 18:20:42 +0000

#3 Caused some issues for me and Mike Busch. Even in noConflict mode there can be conflicts. I’m looking at you prototype, overriding javascript methods that another library might use.

Comment on JavaScript Best Practices by jasonkarns

Wed, 03 Mar 2010 18:11:08 +0000

@nerdstrap76 I definitely agree with the braces. Although one-line if statements look elegant, they usually introduce bugs when being maintained. Another reason to use JSLint!

Comment on JavaScript Best Practices by nerdstrap76

nerdstrap76 — Wed, 03 Mar 2010 16:03:13 +0000

Always use brackets for if-then-else, while and for loops! That way your code can be minimized and de-minimized without introducing logic errors!