!== and === are identity operators. It is a good idea to use them
instead of the equality operators (!= and ==) unless you know why you
would want to use equality (and the possible type coercion) over
identity. Probably the biggest gotcha with equality is with falsy
values (false, 0, undefined,
Then, there's that nasty two bugs: [...] and quirky animation in FF.
From what I have seen, the animation issue should be resolved with
1.1.3. Give one of the recent nightly builds a spin to make sure your
issue is fixed though.
Ian
On 5/9/07, Dragan Krstic <[EMAIL PROTECTED]> wrote:
But,
You can also try to attach a single event handler to the root node of
your tree and then only process the clicks on A-tags.
function iEatEventsForBreakfast(event) {
var target = $(target.event);
if (target.is("a")) {
// search for and open/close the folder associated with target
// somet
On 4/28/07, Michael Geary <[EMAIL PROTECTED]> wrote:
Indeed there is, return false. See my #1 example which is similar to
yours...
I should have used my eyes before I started typing. My question's
code is almost exactly what you wrote, just cosmetic differences. I
missed the assignment + ret
Thanks Ian, it seem to be working perfectly. I just have one more
question: isn't there a big performance impact using this piece of
code? It looks like the page it taking a while do load, but I guess
you have to choose between the time the page takes to load and the
time you take to do every
The event is not passed down to the underlying event but rather it
bubbles up through the dom tree from the event where the event was
triggered.
http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-flow-bubbling
An example is probably easier to digest. This code has click handlers
at bod
Building on Karl's example and your new all-td's-must-be-empty
requirement; mark all the TR's with a target class then sweep through
the TD's and get rid of the target class if you find a td that is not
empty. Play around a bit and see what else you can come up with.
Ian
$(document).read
At the risk of beating a dead horse; a few links to related (and
fixed) bugs in other projects (including firefox).
The root cause of the hack (Dan just touched on it):
https://bugzilla.mozilla.org/show_bug.cgi?id=246651
Message reporting that the above bug was fixed in the 11 Sep 2004 build :
Ditto :)
On 4/10/07, Ⓙⓐⓚⓔ <[EMAIL PROTECTED]> wrote:
thank you John, it always bothered me!
On 4/10/07, John Resig <[EMAIL PROTECTED]> wrote:
>
> Personally, I think this fix should just be removed - especially
> considering that we don't even support versions of Firefox, that old,
> any more.
Correct, this was a work around for a pre-1.5 FF issue. My notes on
it say "see mozilla bug #246651" but I remember thinking that jQuery
was using the same work around as another js library (prototype?) and
that that project had its own bug to get rid of the work around. I
thought I saw that th
10 matches
Mail list logo
