The ID shouldn't be necessary at all ... it just provides some context to
make the selector faster. I'll try out your example soon to see if I can
spot the issue.
--
Brandon Aaron
On 8/28/07, Theodore Ni <[EMAIL PROTECTED]> wrote:
>
> I know exactly what you mean, and it makes perfect sense, and
Just in case anyone wants to see, this is the test script that I used. Just
change the filenames to whatever you want:
Testing Dragging
$(document).ready(function() {
// I'd think that this would work
$('form.client').livequery('submit', function() {
alert($(this).find('[E
I know exactly what you mean, and it makes perfect sense, and now going back
to Firefox, it works like a charm. Normally that would be enough for me, but
this needs to run in the exploder :-(
Ok, I've gone back and tried to recreate this example, and you are right,
the selector works if I add in a
That sounds like it should work, but it isn't doing anything. I think
there must be something wrong with my fundamental understanding of how
jQuery or the plugins work.
Suppose I try this:
$('form.client').livequery(function() {
//alert('new: ' + $(this).parent().attr('id'));
$(t
Just use Live Query to bind the submit handler. It will only bind it once
per a new form element.
$('form.client').livequery('submit', function() { alert('boo'); return
false; });
Also, try to give the selector more scope, like a parent element with an ID.
$('#containerID form.client').livequery
I'm not very familiar with the Interface library but it looks like the
Draggable code clones the element using native DOM methods. Try registering
the Draggable plugin via the registerPlugin method (
http://brandonaaron.net/docs/livequery/#plugin-developers) like this:
$.livequery.registerPlugin("
6 matches
Mail list logo
