Richard Gibson

I'm not talking about element tests (which are always `nodeType === 1`), but about _node_ tests, for which we have no standard (and in practice use boolean-cast `nodeType` _almost_ exclusively,...

Ugh, I am so sick of these scrollbar-related dimensions issues. What's happening here is that in the affected (i.e., non-Firefox) browsers, elements with `box-sizing: content-box` do not include scroll gutters...

The ones that were altered and/or deleted for IE \

Firefox reports no boxes for \ elements: https://jsfiddle.net/u82u24z2/9/ . I don't think this is our problem to fix.

@bzbarsky As it turns out, Firefox _does_ eventually report `ClientRect`s—provided the map is in use: https://jsfiddle.net/u82u24z2/12/ . The asynchronicity is a little weird, and you may want to look into...

It is intended for [2.x compatibility](https://github.com/jquery/jquery/blob/5c01cb1cc4a41b29d6739d061de8217c33037639/test/unit/deferred.js#L660-L663), which loomed much more heavily when the code was written. Now, I've had all the fight beaten out of me on this point, much...

Compatibility with [jQuery 1.x/2.x](http://api.jquery.com/deferred.resolve/) ("Each callback is passed the args from the `deferred.resolve()`"). Also, if we do want to introduce initial resolution unwrapping, we'll have to: - specifically look _only_...

For posterity, the cases I consider most important to address: ``` js var badThens = [ function() { throw new Error(); }, function( onFulfilled ) { onFulfilled( "foo" ); throw...

@Krinkle you're smack in the middle of the legacy–standard interface here, which is why behavior is odd. The crux of it is that "the promise is actually resolved with another...

Thanks, I moved the documentation needs to https://github.com/jquery/api.jquery.com/issues/1039 . And I guess I'll keep this issue open until we either always unwrap thenables, or decide not to make that change.