arf, crossposting, where is that damn coffie ? :)
On 21 jan, 09:43, Alexandre Plennevaux [EMAIL PROTECTED] wrote:
Matt, just a remark: if you do need to add that click behaviour to P
elements not existing at the time of the call, there is a nice plugin:
livequery that does that.
On 21 jan,
Matt, just a remark: if you do need to add that click behaviour to P
elements not existing at the time of the call, there is a nice plugin:
livequery that does that.
On 21 jan, 06:02, Matt Quackenbush [EMAIL PROTECTED] wrote:
Karl,
Thank you, thank you, thank you, thank you, thank you, and
Don't forget you could also just bind a click event to a parent
object.
That way any click in a child element, old or new, will bubble up and
trigger the click event. In the event handler, just inspect
event.target to see which child was clicked.
George
From what you described, you are adding the element after you have bound
an event.
So your code is really doing:
1. bind function to click event of some element
2. add some element to the dom
you can clearly see the event wont get attached to the element.
you'll either have to call the code
Okay, in my continued pursuit of finding out what I've done wrong, I
hard-coded into the html a block identical to the one that jQuery adds to
the DOM via the Add an Item link/button. When using this, my Remove this
Item button/link works perfectly.
In addition, I am using the Highlighter plugin
After a brief read I think you're running up against a common
misconception about how jQuery attaches events to objects.
When you do something like this:
$('p').click( function() { alert('blah'); } )
All the _currently existing_ 'p' elements will have a click handler attached.
Now if you go
Karl,
Thank you, thank you, thank you, thank you, thank you, and THANK YOU!
By the way, in case I forgot, please, let me be sure to say Thank you!
before signing off.
Thanks,
Matt
On Jan 20, 2008 9:53 PM, Karl Rudd wrote:
You might like to look at the LiveQuery plugin (
7 matches
Mail list logo
