Comments for Paul Irish

Comment on Avoiding the FOUC v3.0 by How do I create a jquery function that will override my css hover while javascript is enabled? | Easy jQuery | Free Popular Tips Tricks Plugins API Javascript and Themes

Mon, 21 May 2012 07:22:48 +0000

[...] : http://paulirish.com/2009/avoiding-the-fouc-v3/ for more [...]

Comment on Debounced resize() jQuery plugin by window.resize in jquery firing multiple times | Easy jQuery | Free Popular Tips Tricks Plugins API Javascript and Themes

Mon, 21 May 2012 06:57:36 +0000

[...] You got it, some browsers fire on resize start and again on end while others like FF fire continuously. Solution is to use setTimeout to avoid firing all the time. An example can be found here. [...]

Comment on 10 Things I Learned from the jQuery Source by Vinch

Vinch — Sat, 19 May 2012 17:51:40 +0000

Interesting fact here: http://cl.ly/0Q1I410M1s0n2z383J2X
Only class and for are quoted because they are reserved words in JavaScript (even though class is useless right now and is reserved for a possible future use…)
My 2 cents.

Comment on * { box-sizing: border-box } FTW by karthipanraj

karthipanraj — Sat, 19 May 2012 10:50:26 +0000

Really Nice post and comments. More Informative

Comment on Cornify Konami easter egg plugin with jQuery by Konami Edit: a jQuery plugin for [Contenteditable] | Frank M Taylor

Konami Edit: a jQuery plugin for [Contenteditable] | Frank M Taylor — Sat, 19 May 2012 00:06:56 +0000

[...] that, you activate the plugin with the Konami Cheat. I'll freely admit that I'm usingPaul Irish's code that he wrote for a Cornify easter egg a few years ago. Type the Konami cheat, and then double-click any element you want to edit [...]

Comment on Conditional stylesheets vs CSS hacks? Answer: Neither! by Paul Hagan

Paul Hagan — Fri, 18 May 2012 10:17:58 +0000

Just found what might be a fiddly little bug with this trick in IE on Windows Phone.

For whatever reason it appears that it causes the browser to ignore and/or incorrectly interpret CSS media queries. Some kind of Quirks Mode issue? Who knows. Anyway – couple of examples…

Page without the trick. H1 should have a blue background on small screens, and red on larger screens. Works fine on all browsers including IE9 windows phone.

http://dl.dropbox.com/u/2042220/open-day/windows-mobile-test-no-trick.html

Page with the IE class trick applied – H1 gets no background colour at all. Very odd.

http://dl.dropbox.com/u/2042220/open-day/windows-mobile-test-html-trick.html

Page with the IE class trick moved to the tag instead, and everything is back to working fine.

http://dl.dropbox.com/u/2042220/open-day/windows-mobile-test-html-trick-on-body.html

This is a basic example, but since adding a Windows Phone to my testing kit it’s shown me that basically all my responsive sites that use this approach are knackered on windows phone – although interestingly, respond.js seems to fix it if it’s present…

I know Windows Phone is only a small market share at the moment, and I’m not particularly a fan of it myself, but it does a pretty good job of rendering responsive sites that don’t use this approach so would be a

Comment on * { box-sizing: border-box } FTW by alo

alo — Thu, 17 May 2012 22:28:23 +0000

Chrome 19 breaks box-sizing: border-box when the following style is used: 'display: table; table-layout: fixed'

http://code.google.com/p/chromium/issues/detail?id=124816

Comment on Talk: Tooling & The Webapp Development Stack by Micah

Micah — Thu, 17 May 2012 00:23:50 +0000

My stack:
HTML5Boilerplate
Jade, Sass, Compass, Susy
jQuery
Coda, Codekit (which includes linting, minify, contatination and image optimization), Chrome
MAMP, Github

Comment on @font-face gotchas by i believe in concept

i believe in concept — Wed, 16 May 2012 19:53:15 +0000

[...] Paul Irish's article (This article also appears on "I Believe In Design") This entry was posted in Web Design. Bookmark the permalink. ← Branding the Home Tour [...]

Comment on Talk: Tooling & The Webapp Development Stack by Aaron Barker

Aaron Barker — Wed, 16 May 2012 14:46:40 +0000

Was cool to see the quick history of the tools. I helped make a tool to inspect the DOM in 2004 that was pretty spiffy for the time.

http://slayeroffice.com/?c=/content/tools/modi.html

Not sure how popular it was, but sure saved me hours of debugging time and predated the one you listed from 2006 :)

Comment on 10 Things I Learned from the jQuery Source by Pierre

Pierre — Sat, 12 May 2012 16:03:51 +0000

Question about the "asynchronous recursion": isn't this creating infinitely deep stack traces? (since we're never leaving the current context frame when calling the function again) And would this potentially cause problems?

Comment on Talk: Tooling & The Webapp Development Stack by Nick Knowlson

Nick Knowlson — Thu, 10 May 2012 22:17:05 +0000

Anyone know where those two charts that showed and organized a bunch of javascript libraries are at? There was one that had a lot of them, and then a smaller one by someone from Dojo.

Comment on How to fulfill your own feature request -or- Duck Punching with jQuery! by Brian

Brian — Thu, 10 May 2012 15:34:07 +0000

@JDub
I've run into this specific issue when using the jQuery UI tabs. Our solution was to wrap the code in a try..catch, ala:

(function($){
    var _old = $.unique;
    $.unique = function(arr){ 
        // do the default behavior only if we got an array of elements
    	try {
	        if (!!arr[0].nodeType){
	            return _old.apply(this,arguments);
	        } else {
	            // reduce the array to contain no dupes via grep/inArray
	            return $.grep(arr,function(v,k){
	                return $.inArray(v,arr) === k;
	            });
	        }
    	}
    	catch (e){
    		return _old.apply(this,arguments);
    	}
    };
})(jQuery);

This way, if there is any failure in the punched duck, the original code is run regardless…

Comment on Conditional stylesheets vs CSS hacks? Answer: Neither! by Frank Stallone

Frank Stallone — Thu, 10 May 2012 12:41:03 +0000

@Stolice No problem. Note that I did not include a .ie6 because the conditional comment was for less than (or later than, however you interpret it) ie7. A class of .lt-ie7 works just fine here in this case. I am pretty satisfied with this solution and would be interested in seeing how it could be improved in the future.

Comment on * { box-sizing: border-box } FTW by Edson

Edson — Thu, 10 May 2012 11:50:03 +0000

@Tiery Thank you Tiery! I didn't realize that "border-box" also affect the height of an element. I appreciate your tip!