Very cool!
Jörn
On Sat, Jan 24, 2009 at 8:37 PM, David Zhou da...@nodnod.net wrote:
I've now updated the app to be able to use QUnit:
http://jquery.nodnod.net/cases/38
As usual, I've also pushed the latest changes to github.
(http://github.com/dz/jquerytester/)
-- dz
On Fri, Jan 23,
Hi, I have found some issues in how jQuery 1.3.1 handles checkboxes in
XHTML. I created the following PHP sample based on jQuery FAQ 1.7:
?php
header('Content-type: application/xhtml+xml');
print '?xml version=1.0 encoding=iso-8859-1?' . \n;
?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML
I've had a similar problem with version 1.3.1 ！
It was found in UI/Effects/Transfer. When target element with
display:none ,the function offset() return zero-valued top and left.
I've had found a temporary way to solve the problem.
/
jQuery.iUtil = {
Feature detection is definately the way to go *when applicable*, so
$.support is a great addition to jQuery.
However, I question the decision to depricate $.browser so abruptly.
This *forces* jQuery developers to create 'hacks' when feature
detection is not the best solution. The discussion here
Hi Kevin,
While I appreciate your concerns, I think you're operating under a
mistaken notion of what deprecation means. The $.browser method
still exists. The whole idea of deprecation is to allow a transition
period:
cf. http://en.wikipedia.org/wiki/Deprecation
Although deprecated
While I appreciate your concerns, I think you're operating under a
mistaken notion of what deprecation means. The $.browser method
still exists. The whole idea of deprecation is to allow a transition
period:
Further, it *is* possible to be properly compatible with both 1.2.6
and
So, I've started the process of converting to jQuery. But, I think
there is a snag. I noticed that you can't cancel events. Is this on
the horizon? In JMVC, I collect all the elements that respond to the
event through delegation and order them. I dispatch each callback,
but if the event's
