It seems like the latest qunit doesn't have working modules, is this a
known issue? (commit: 57d1a28a9f6c44204d46ad651711beb4f8642117)
Looking at the code, it seems to have been broken due to commit
25c0a978997c8be12c7ea39abf919403a06f7473
The fix is just as simple, adding that one line back in m
I support this as well.
On 2009-10-28, at 3:15 PM, Nathan Bubna wrote:
> ditto.
>
> On Wed, Oct 28, 2009 at 8:00 AM, weepy wrote:
>>
>> i strongly support this.
>>
>> to my mind the notion that you can exclusively apply feature
>> detection
>> to the extremely complex browsers is optimistic.
>
ditto.
On Wed, Oct 28, 2009 at 8:00 AM, weepy wrote:
>
> i strongly support this.
>
> to my mind the notion that you can exclusively apply feature detection
> to the extremely complex browsers is optimistic.
> there just too many features and special cases to handle.
>
> On 28 Oct, 12:09, jez
i strongly support this.
to my mind the notion that you can exclusively apply feature detection
to the extremely complex browsers is optimistic.
there just too many features and special cases to handle.
On 28 Oct, 12:09, jez wrote:
> Sorry to reignite this debate in a new thread rather than
Sorry to reignite this debate in a new thread rather than replying to
the old one, but for some reason Google Groups wouildn't let me reply
to the old one. The suggestion was that the jQuery documentation be
reworded so that $.browser not be called 'Deprecated', but that its
usage perhaps be disc
