unpacking a mutation observer callback

[xelawho]

ha, ha. I figured it out finally, and of course it's obvious when you look at it and has nothing to do with what I thought it did.

Here's the thing: the form (or whatever it is) gets submitted via the click on the button. So adding another click listener puts that second listener at the end of the queue, and the function fires too late (I don't know how this fits in with LIFO, or maybe I just don't understand LIFO).

But of course using mousedown means you get to sneak in before the click function fires and do your validation routine.

Thanks for sticking with me, though, rnd me. It was an interesting discussion regardless.

[rnd me]

Well, I never give up, especially for fellow regulars. I've always found jQuery events incredibly complicated and confusing when it comes to working on them from the outside. With event attribs, you can see what's doing what, but jQuerys are invisible and hard to control. Especially when you have to adjust a fully-implemented site you didn't create, it can be a bear.

Earlier in my career, i had a related problem that drove me to the edge of sanity: Ihad to clone and hide a button in order to add the event up-front. Once the clone's click was complete, it dispatched a mousedown(), click(), and mouseup() to the orig but now-hidden button. A convoluted workaround for sure, but one that ultimately bought six more months until a site rebuild.

Anyways, glad it's resolved...

[xelawho]

Originally Posted by rnd me

I've always found jQuery events incredibly complicated and confusing when it comes to working on them from the outside. With event attribs, you can see what's doing what, but jQuerys are invisible and hard to control.

ha! pretty much the topic of my other post - it works, I just don't know why. Which for some reason I find even more frustrating than the other way 'round...

[AndrewGSW]

@rnd me

With event attribs, you can see what's doing what, but jQuerys are invisible

? Don't we have the event attributes available..?

$("#target").click(function (e) {
  console.log(e);
});

Or perhaps this is a tweaked version of the event object?

[rnd me]

Originally Posted by AndrewGSW

@rnd me


? Don't we have the event attributes available..?

$("#target").click(function (e) {
  console.log(e);
});

Or perhaps this is a tweaked version of the event object?

you show an event argument, not an attribute.

it the difference between debugging this:

<input value=ok type=button />

and this:

<input value=ok type=button onclick="addSelectionToList()" />

based on the desire of "semantic documents" javascript was moved from binding ui inline to external files. While it might make librarians happy, the practice is frustrating to people who maintain web apps.